Downloads - Photo Site Links
DBCSS : Manage Meta tags, stylesheet and scripts
As you know, Pico allow you to include specify the module html header, categoriy and sub-category header, but the most interesting each document html header.
But not all modules are so friendly with site owners ^^ That's where DBCSS is so useful. The module will allow you override module header to be able to compile meta tags, javascript and stylesheet through anintuitive User Interface
SDCSS is a module based on Duplicatable V3
The module comes with the following functions:
- The stylesheet can be compiled within module header operating alike the alternative system module "altsys" by GIJOE - Block management, the stylesheet can be applied to an optional page - Easily import the CSS file as a DB template - Easily export the stylesheet compiled within this module - Apply compiled META tags to each module - As a D3 module,you can easily rename directory and have nultipleinstallations
Furthermore, this module requires Altsys to be installed and XOOPS_TRUST_PATH defined on your mainfile.php
Module source code ref to d3blog, altsys and hodaka by GIJOE
Comments (5)
Has anyone managed to get DBCSS working correctly with 2.0.18.1?
I already have a bunch of GI Joe's stuff running (i.e. xoops/trust/path/ protector, altsys, etc) It installs and seems to run (no errors on debug) just fine but when I check my source on pages I get:
Looks like it is there but when I check the source meta name="description" the same metadata generated from Xoops core.
Is there something different in Xoopscube theme or template that needs to be changed for Xoops?
BTW: There is also nothing in the installation instructions about creating a /common/ directory in the site root. I did that manually but still no luck.
Read Me file is not in english
(a fan but still not ready to switch entire platform to xoopscube)
Apache/1.3.37 (Unix) mod_throttle/3.1.2 DAV/1.0.3 mod_fastcgi/2.4.2 mod_gzip/1.3.26.1a PHP/4.4.8 mod_ssl/2.8.22 OpenSSL/0.9.7e
PHP version 5.2.3 MySql version 5.0.24a-standard-log
Has anyone managed to get DBCSS working correctly with 2.0.18.1?
I already have a bunch of GI Joe's stuff running (i.e. xoops/trust/path/ protector, altsys, etc) It installs and seems to run (no errors on debug) just fine but when I check my source on pages I get:
Looks like it is there but when I check the source meta name="description" the same metadata generated from Xoops core.Is there something different in Xoopscube theme or template that needs to be changed for Xoops?
BTW: There is also nothing in the installation instructions about creating a /common/ directory in the site root. I did that manually but still no luck.
Read Me file is not in english
(a fan but still not ready to switch entire platform to xoopscube)
Apache/1.3.37 (Unix) mod_throttle/3.1.2 DAV/1.0.3 mod_fastcgi/2.4.2 mod_gzip/1.3.26.1a PHP/4.4.8 mod_ssl/2.8.22 OpenSSL/0.9.7e
PHP version 5.2.3 MySql version 5.0.24a-standard-log
Hi techdb,
Welcome to XOOPS Cube !
No big changes within theme nor templates. But the render was clean rewrite by Minahito he has bloged and made a video about Legacy.
I give a try to 2.0.8.1 and 2.3 but both releases still far from Legacy.
So, until the promised Xoops 3 it's a waste of time to push further testing. Even more with icms who also starts to implement Legacy features alike "Preload" or XOOPS_TRUST_PATH
But if you have free time enough, go for it, and share your experience. People will be glad if you do so ^^
Most of all, keep having fun whatever you do!
So, until the promised Xoops 3 it's a waste of time to push further testing. Even more with icms who also starts to implement Legacy features alike "Preload" or XOOPS_TRUST_PATHBut if you have free time enough, go for it, and share your experience. People will be glad if you do so ^^
I am like everyone looking forward to a more stable core. Module really looks like it is compatible... I even think there are instructions in the Read ME file however for some reason I can't translate the Read ME file with altavista.
Any chance someone could get the read me file in english?
So, until the promised Xoops 3 it's a waste of time to push further testing. Even more with icms who also starts to implement Legacy features alike "Preload" or XOOPS_TRUST_PATH
But if you have free time enough, go for it, and share your experience. People will be glad if you do so ^^
I am like everyone looking forward to a more stable core. Module really looks like it is compatible... I even think there are instructions in the Read ME file however for some reason I can't translate the Read ME file with altavista.
Any chance someone could get the read me file in english?
Hi,
If you're looking for a more stable core - you just find it ^^
Seriously, you should acknowledge that Xoops.org has to
much patchwork since the core was developed by Mithrandir
then Skalpa.
There's a lot to fix and to implement in Xoops2 to reach Legacy
coded by skilled programmers. Same for D3 modules,
XOOPS_TRUST_PATH, /common, etc. are all concepts
of XOOPS Cube core developers.
This D3 module requires Altsys which seems to not run smoothly
on xoops.org releases.
Cheers
