82
As you can see in the code above, you are not calling any text but using an image (poweredby.gif) for the footer. If you want to use the footer entered in the "Meta Tags and Footer" admin, you have to use the Smarty variable <{$xoops_footer}>.
The default theme uses the image and not the Smarty variable.
Hope this helps!
The default theme uses the image and not the Smarty variable.
Hope this helps!
83
Yes you should.
We need to make distinctions between permissions and block settings. Set permissions through Sys Admin > Groups. Define which groups sees which block.
Then, from Sys Admin > Blocks, define how the blocks will be rendered (visibility, weight order). Sometimes, you give permission to a block, but it does not necessarily have to be visible.
Maybe this link will help explain it:
Modifying Blocks
We need to make distinctions between permissions and block settings. Set permissions through Sys Admin > Groups. Define which groups sees which block.
Then, from Sys Admin > Blocks, define how the blocks will be rendered (visibility, weight order). Sometimes, you give permission to a block, but it does not necessarily have to be visible.
Maybe this link will help explain it:
Modifying Blocks
85
Ok, these links will help you understand your situation:
Placing Blocks
Custom Block
News Module Help
Block positioning question
Placing Blocks
Custom Block
News Module Help
Block positioning question
86
Your no. 2 solution could work, but may I just suggest you go to Sys Admin > Preferences > General Settings and set "Module for your start page" to News?
87
Hmm...that would be one way of editing templates and putting permanent changes. But that would be going about it in the wrong way.
The default templates are uneditable and cloned so as to 'preserve' the originals, just in case something goes wrong. XOOPS actually calls the templates from the DB, thus, in your case, you had to update the module after you edited the HTML files for the changes to reflect in the site. Updating sent the HTML files into the DB.
That is why you have to clone the templates--to create another set in the DB that will be used and called by XOOPS. Editing the HTML files directly would be 'unorthodox' and inefficiant, to say the least.
The default templates are uneditable and cloned so as to 'preserve' the originals, just in case something goes wrong. XOOPS actually calls the templates from the DB, thus, in your case, you had to update the module after you edited the HTML files for the changes to reflect in the site. Updating sent the HTML files into the DB.
That is why you have to clone the templates--to create another set in the DB that will be used and called by XOOPS. Editing the HTML files directly would be 'unorthodox' and inefficiant, to say the least.
88
Quote:
Smarty is basically 'on' with the XOOPS installation. The next step would be to enable caching. Caching can be module wide (from Sys Ad > Prefs > Gen Settings) or block/template specific (from Sys Ad > Blocks > Edit a block).
Here's an example: For my site, I disabled comments for MyLinks. Since I usually put the new links, and approve all link submissions, I set module cache to 3 days. This would mean that once a page is called by a user, it stays in cache for 3 days. If I get a submission, or upload a new link, I just update the DB from Sys Ad > Prefs > Gen Settings, to refresh cache.
Note: if you have enabled comments in cached modules, it will not be shown until the cache is refreshed according to time specified. Users will notice a delay in the display of their comments. They might report a bug to you about this when it was just a cache issue.
sud_crow wrote:
Do you recommend setting Smarty on??
Smarty is basically 'on' with the XOOPS installation. The next step would be to enable caching. Caching can be module wide (from Sys Ad > Prefs > Gen Settings) or block/template specific (from Sys Ad > Blocks > Edit a block).
Here's an example: For my site, I disabled comments for MyLinks. Since I usually put the new links, and approve all link submissions, I set module cache to 3 days. This would mean that once a page is called by a user, it stays in cache for 3 days. If I get a submission, or upload a new link, I just update the DB from Sys Ad > Prefs > Gen Settings, to refresh cache.
Note: if you have enabled comments in cached modules, it will not be shown until the cache is refreshed according to time specified. Users will notice a delay in the display of their comments. They might report a bug to you about this when it was just a cache issue.
89
Hi nickt,
If it's not too confidential, could you post the code that goes into the custom block? I would like test it in my home XOOPS setup. Others might want to try it too.
Thanks!
If it's not too confidential, could you post the code that goes into the custom block? I would like test it in my home XOOPS setup. Others might want to try it too.
Thanks!
90
Hi risto,
I'm sorry but I don't think that feature is available in the current newbb.
Check out this link for updates on the new version of newbb:
Report about the NewBB
I'm sorry but I don't think that feature is available in the current newbb.
Check out this link for updates on the new version of newbb:
Report about the NewBB
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | May 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|