Cool! Looking great

Hi webmaster!

I noticed i had 2 Xoops rss-feeds in my rss-reader.
- xoops.org/backend.php which feeds me news from 2017 from /modules/news
and
- xoops.org/modules/publisher/backend.php which server the recent news-articles.

Maybe we should use only one news-module and rss-feed

Happy Xoops-ing!

Found something: I presume when you have, like me, three languages you can change the order with the admin-option weight?
I started with English, added dutch and then french. And set the weight to 2, 1 and 3. But nothing changes. Could be i don't understand what weight should be doing, but I hoped it would change the order, or at least that an unknown visitor would see dutch first...

Yes! Finally a version that works! Thank you Mamba

The part about "Upgrading from previous versions older than 2.5.5 (Full Update)" but also the documentation inside the "xoops-2.5.6_full_upgrade.zip"-package in the "release_notes.txt" (paragraph "Upgrading from versions older than 2.5.0:") states:
File Normal For upgrade
mainfile.php 400 700
/include/license.php 444 777

but i think that should be:
File Normal For upgrade
mainfile.php 444 777
/include/license.php 444 777

because my site stopped working

But on the good side: upgraded from 2.4.5 to 2.5.6 with no problems with the instructions from forementioned paragraph, thanx! Very good!

@mboyden: you can see in the listed paths in my previous message that i'm already using those paths.

@sabahan: i'm aware of theme overriding. That is the same thing the templates manager is for. The templates manager generates specific templates (you choose in the templatesmanager) and generates the files you need in the selected theme. After generation you can edit the template online (which is a great enhancement of Xoops2.5, I think).

But what permissions does the webserver need to generate, well actually save, those files on the server. Because if that is 777 than anyone can save new templates including possible some mailicous injections in those template-files.

PS @ForMusS: Thanx, if you want more info, i'm still testing

I really love the new Xoops version! Especially the new admin-interface give Xoops the professional look of a serious cms.

I'm trying to use the Templates manager in xoops 2.5.1a (with PHP 5.2.17) to make custom templates for another theme i created. But i can't generate the templates for this theme. It seems it has to do with permissions on the filesystem or so.

What i found out so far:
- all files/directories are owned by me
- if i choose my theme / forced file generation - yes / all modules (only system and fmcontent) i get the message 'no files generated'
-> this is good because file permissions are not set to allow this.

adjustment 1:
- i chmod the directory /themes/mytheme/modules to 757 (apache should be able to write here now)
- if i choose mytheme / forced file generation - yes / Select modules (only fmcontent), i select all shown files, the template-files for fmcontent are generated (owned by apache)
- the templatesmanager shows these files and the subdirectory blocks but inside blocks no files are generated.

adjustment 2:
- i chown the directory /themes/mytheme/modules/fmcontent/blocks to myself and set permission on this directory to 757 again
- after choosing mytheme / forced file generation - yes / Select modules (only fmcontent), i select all shown files, all block-files for fmcontent are generated (owned by apache)
- the templatesmanager shows these files now.

* Is this normal for the Xoops Templatesmanager?
* How should i apply permissions to the files? The template files are now world-writeable, but if i chown them to myself i can't edit the files!

Any comments?

Eventually found this while i had actually already abandoned this module: you need an extra Framework: modulesadmin. Can be found here:http://www.freexoopservices.com/modules/TDMDownloads/singlefile.php?lid=3

Documentation how to install is included!

Menu works now...

@Voltan: maybe something to put in a readme?

Yeah, i'd like to help!

Great! Now i can upgrade without extra steps


In the Trunk there still exists a readme.txt that gives the old instructions (hackin into common.php). Maybe that should be deleted too?