after update to 1.8.3 on PHP Version: 5.5 I have the issue that whenever i click on a contentpart teaser or try to create one the admin page (phpwcms.php) renders empty.
Source-code rendered is simply blank.
I already tried to delete all scripts and created special template with only RT:CONTENT, problem stays unchanged...
just installed a fresh v1.8.3 on the server. The setup process doesn´t even let me create an admin account...
it is creating it by itself but doesn´t show any username or password option fields during the process...
its a limitation in the amount of articles that the CP:Teaser can list in the backend.
as soon as i deleted a category with about 200 articles - it was working again.
i tried this with a re-imported database and deleted another category just to make sure it was not a non-compatible character in the article titles (i had something similar in the past...) - it worked normal again.
This Bug seems to appear only in newer versions of phpwcms - up to v1.7.9 it works great!
The system contains about 4850 articles - is there a work-around for this issue?
But this comes up:
PHP Notice: Undefined index: maxlength in /is/htdocs/wp1176637_1Q3Q5RT5PF/www/include/inc_front/content/cnt23.article.inc.php on line 1027
but it´s in no relation to the system that is having trouble with the teasers, since it sits in another subfolder of the server...
(which would be /is/htdocs/wp1176637_1Q3Q5RT5PF/www/mediacenter/include/....
Could this problem be related to the CSRF Measure you integrated into the system with v1.8.0?
I´m simply guessing since those Security Measures were the main Change for this version... ??
I would like to mention that i really appreciate your help!!!
Do not know which release of phpwcms you use, but it is outdated. That notice is impossible in current release (and also at another line of code).eccentric.worx wrote:PHP Notice: Undefined index: maxlength in /is/htdocs/wp1176637_1Q3Q5RT5PF/www/include/inc_front/content/cnt23.article.inc.php on line 1027
CSRF has no effect in frontend, neither at that place in the backend.
Maybe its easier this way:
i run 2 systems in 1 domain...
root (system that produces the PHP Error message) PHPWCMS v.1.7.9
subfolder (system which has the Teaser Problem - no PHP Error) PHPWCMS v1.8.3
i tried yesterday by upgrading a test-system (version to version) to find out which ones are affected - every release following the v1.7.9...
I cannot help here without having a view on real data.