[SOLVED] Blank backend screen after updating/adding pages

[nils73]

Hi everybody,

after uploading the last patch from 1.11.9 to 1.11.10 there is a strange behaviour with my backend: whenever I add or update pages I get a blank screen. I remember that I had this problem years and years ago with v1.4 but whatever I did id just didn't solve the problem. Tried cleaning the template-c and even re-uploaded the files for the update.

Here is the copied system-information:
----------------------------------------------
Cms Version: 1.11.10
Installed Modules:
CMSMailer: 5.2.2
Gallery: 1.6.1
FileManager: 1.4.4
MenuManager: 1.8.6
MicroTiny: 1.2.6
News: 2.14.2
Guestbook: 1.4_RC2
FormBuilder: 0.7.4
CGExtensions: 1.37.3
CGFeedMaker: 1.0.19
SiteMapMadeSimple: 1.2.7

Config Information:
php_memory_limit:
process_whole_template:
max_upload_size: 2000000
url_rewriting: mod_rewrite
page_extension:
query_var: page
image_manipulation_prog: GD
auto_alias_content: true
locale:
default_encoding: utf-8
admin_encoding: utf-8
set_names: true

Php Information:
phpversion: 5.3.3-7+squeeze19
md5_function: An (Ja)
gd_version: 2
tempnam_function: An (Ja)
magic_quotes_runtime: Aus (Nein)
E_STRICT: 0
E_DEPRECATED: 0
memory_limit: 128M
max_execution_time: 30
output_buffering: 1
safe_mode: Aus (Nein)
file_uploads: An (Ja)
post_max_size: 8M
upload_max_filesize: 2M
session_save_path: Keine Prüfung, da eine „open basedir“-Beschränkung aktiviert ist
session_use_cookies: An (Ja)
xml_function: An (Ja)
xmlreader_class: An (Ja)

Server Information:
Server Api: apache2handler
Server Db Type: MySQL (mysql)
Server Db Version: 5.1.73
Server Db Grants: Gefunden eine "Alles gewähren"-Anweisung, die als geeignet scheint
Server Time Diff: Keine Abweichung der Zeit im Dateisystem gefunden

----------------------------------------------

Any hint would be welcome.

Thx
Nils

Topic was: Blank backend screen after updating/adding pages in 1.11.10

[velden]

Usually a blank screen indicates a fatal (php) error which is suppressed by some setting.

So find out what the error is by:

- enabling php error reporting
- looking at the php/apache error logs

(Those are no options of cmsms but of your webserver/hosting provider).

When you know what the actual error is let us know.

[nils73]

Thank you. Just enabled error-logging and got this result:

PHP Fatal error: Uncaught --> Smarty Compiler: Syntax error in template "module_db_tpl:SiteMapMadeSimple;xml_Sitemap-plus-News" on line 17 "{capture assign='junk'}{news number='1000'}{/capture}" unknown tag "news" <--

Well, if I disable SiteMapMadeSimple then the error is gone - but as far as I can see there is no real error in using capture and news. So for now I disabled SiteMapMadeSimple until I find a solution to this.

Regards
Nils

[Jo Morg]

Try

Code: Select all

{news number='1000' assign='junk'}

or

Code: Select all

{News number='1000' assign='junk'}

or

Code: Select all

 {cms_module module='news' number='1000' assign='junk'}

or

Code: Select all

 {cms_module module='News' number='1000' assign='junk'}

this, of course, without the capture.

I know that Smarty is case sensitive as of version 3 so that might be the problem...

[uniqu3]

Use cms_module tag and not short plugin tag as back end doesn't know about short module plugin tag, therefore when SiteMapMadeSimple is generated and processed after saving content, Smarty fails due to unknown tag.

[nils73]

Code: Select all

{cms_module module='News' number='1000' assign='junk'}

Tried this and it works.

I know that Smarty is case sensitive as of version 3 so that might be the problem...

I see. Tried as well with "news" instead of "News" and it didn't work. Thanks for pointing this out. No - Thanks a billion! Solved.

Regards
Nils

[Jo Morg]

Use cms_module tag and not short plugin tag as back end doesn't know about short module plugin tag, therefore when SiteMapMadeSimple is generated and processed after saving content, Smarty fails due to unknown tag.

I do get your point and it makes sense, but that would mean that it didn't work before and failed silently, without a fatal error...
And what did change then, from 1.11.9 to 1.11.10, to make it fail fatally?
Just wondering...
Glad it's solved though

[uniqu3]

This behavior exists since 1.11 release, therefore no idea, maybe he didn't edit any pages before last upgrade or what do I know.

[Jo Morg]

...maybe he didn't edit any pages before last upgrade...

AH! Good point.