Following Marks suggestion I would like to add my own small list of bugs I've found on version 1.5.1, as already stated
in this thread:
Bug #1 is an older one from former versions.
Within the page edit view, the preview function doesn't work properly for templates which have more than one content block. The main content block (content_en) does show up in the preview, all other self-defined content blocks don't. This bug is reported back to at least 2006 and still around. It would be so nice to have it fixed.
Bug #2:
Whenever you use "internal Link" as a content-type for a page, you can't choose the very first child in the hierarchy underneath. For example from 1.0 choosing 1.1 is impossible, choosing 1.2 is fine - the 1.1 won't show up in the page tree. This happens with every node in the tree, regardless of the hierarchy depth.
Bug #3 occurs only on a hoster that doesn't allow fopen and php_uname():
A clean installation or an update is not possible due to heavy installation errors during step 2
Code: Select all
Warning: php_uname() has been disabled for security reasons in [/ourpath]/cms/install/lib/classes/CMSUpgradePage2.class.php on line 51
Warning: feof(): supplied argument is not a valid stream resource in [/ourpath]/cms/install/lib/classes/CMSUpgradePage2.class.php on line 51/cms/lib/test.functions.php on line 1138
Warning: stream_get_meta_data(): supplied argument is not a valid stream resource in [/ourpath]/cms/install/lib/classes/CMSUpgradePage2.class.php on line 51/cms/lib/test.functions.php on line 1142
The system information is not working on this hoster, only a blank page shows up. So unfortunately I can't provide you with further details about the system settings or with a bug report because even with debug mode on, the system settings are blank. But I've extracted some interesting details through phpinfo:
Code: Select all
SecureSSI Based on PHP 5.2.8
MySQL 4.1.22
CMSms Installation 1.5.1
Modules
MenuManager 1.5.3
News 2.9.1
nuSOAP 1.0.1
Search 1.5.2
ThemeManager 1.0.8
Xinha 0.1.4
FileManager 0.4.3
PHP Info
allow_url_fopen Off
allow_url_include Off
always_populate_raw_post_data Off
memory_limit 32M
output_buffering 4096
output_handler no value
register_globals On
safe_mode Off
Tokenizer Support enabled
GD Lib bundled (2.0.34 compatible)
magic_quotes_runtime Off
session.cache_expire 180
session.cache_limiter nocache
session.cookie_lifetime 3600
session.gc_maxlifetime 1200
session.name PHPSESSID
This happened after an upgrade from 1.2.5 to 1.5.1. We had version 1.4.1 running quite flawlessly on the same server, so this errors belong to version 1.5.1.
Bug #4: Session time outs, forced system logouts and needed re-login
Regarding upgrades: After this upgrade every once in a while we get logged out and have to login again. This happened especially with the news system and the user group settings. I think the sessions get terminated far too soon, although the system settings for session cache expire are set to 180, the same value as the local installation which works completely okay. I've noticed that this happened when there isn't any action within the browser window. Say you need some time so just look at your admin page, then you click on a menu section - and off you go to re-login. This is really painfull, but only occurs on the server with the above limitations, not at home on a local installation!
Bug #5: Strange errors within news system
This is really strange: Whenever one of my co-workers wanted to add a news, they get a pop-up error message:
Code: Select all
ERROR [createSelect]
Can't find the requested dropdown
There was second one right after that error message but I don't have the appropiate screenshot from that. The strange thing about that is: I don't get these errors within my own browsers, neither Internet Explorer nor Firefox. Both of them get these two messages regardless of their browsers. It has nothing to do with user restrictions, we've checked this by switching login accout. They used my admin account with the same results. I don't understand this. I've de-installed and re-installed news module and re-entered all news (weren't much so it was okay for now), but with same results. Maybe you will find out more about this.
Sorry for reporting so late but all of theses errors occured during the two last days, so this is my first opportunity to report them.
Thank you for your time and effort, dear devTeam!
Best regards
Amendra
and hope that helps... 
Sorry if it's meant to be that way and you have wasted your time 
