1.11.5 Upgrade problem [solved]

Help with getting the CMS CORE package up and running. This does not include 3rd party modules, PHP scripts, anything downloaded via module manager or from any external source.
Locked
User avatar
chrisbt
Dev Team Member
Dev Team Member
Posts: 204
Joined: Sun Sep 05, 2010 6:11 am

1.11.5 Upgrade problem [solved]

Post by chrisbt »

I've today come across the same issue with upgrading two 1.11.4 sites to 1.11.5. The issue found was that both sites admin areas completely broke when 'submitting' a changed page.

Upon 'Submit' all that was output in the admin area was blank page with only html and head tags. Debug did not provide any output after 'Submit' just the blank page. 'Apply' appeared to work fine as did the front-end view of all pages.

I eventually uninstalled a (any) module and reinstalled it and all was fixed. Maybe this is something weird with my particular system config, but just thought I'd post this in case anyone else finds a similar issue.

One site has quite a full set of the CG Ecommerce modules installed and the other does not.

----------------------------------------------
Cms Version: 1.11.5
Installed Modules:
CMSMailer: 5.2.1
CMSPrinting: 1.0.4
FileManager: 1.4.3
MenuManager: 1.8.5
CGExtensions: 1.32.2
ModuleManager: 1.5.5
News: 2.12.12
Search: 1.7.8
ThemeManager: 1.1.8
TinyMCE: 2.9.12
CGSimpleSmarty: 1.6
CGFeedback: 1.5.11
Captcha: 0.4.6
CGFeedMaker: 1.0.17
CGSmartImage: 1.10.7
FormBuilder: 0.7.3
Gallery: 1.6
CGGoogleMaps: 2.4.5
CustomGS: 1.3
ECB: 1.5
GBFilePicker: 1.3.3
ListIt2: 1.3.2
ListIt2FAQs: 1.3.2
MicroTiny: 1.2.5
JQueryTools: 1.2.5
Products: 2.18.4
CGEcommerceBase: 1.3.11
FrontEndUsers: 1.21.2
CustomContent: 1.8.3
CGPaymentGatewayBase: 1.1
Orders: 1.13.3
SagepayGateway: 1.0

Config Information:
php_memory_limit:
process_whole_template:
output_compression:
max_upload_size: 32000000
url_rewriting: mod_rewrite
page_extension: .html
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.18
md5_function: On (True)
gd_version: 2
tempnam_function: On (True)
magic_quotes_runtime: Off (False)
E_STRICT: 0
E_DEPRECATED: 0
memory_limit: 128M
max_execution_time: 120
output_buffering: 1
safe_mode: Off (False)
file_uploads: On (True)
post_max_size: 32M
upload_max_filesize: 32M
session_save_path: /tmp (1777)
session_use_cookies: On (True)
xml_function: On (True)
xmlreader_class: On (True)

Server Information:
Server Api: cgi-fcgi
Server Db Type: MySQL (mysqli)
Server Db Version: 5.0.96
Server Db Grants: Found a "GRANT ALL" statement that appears to be suitable

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

PS: Finally got curious about the naming of releases with “Puerto Ayora” - nice, love the idea. Maybe 'Aotearoa' one day :)
Last edited by chrisbt on Wed Mar 27, 2013 3:19 pm, edited 1 time in total.
calguy1000
Support Guru
Support Guru
Posts: 8169
Joined: Tue Oct 19, 2004 6:44 pm

Re: 1.11.5 Upgrade problem

Post by calguy1000 »

A white screen (or 500 error) indicates that there is some kind of php error. We can't help without knowing what that error is.

a: Debug mode
(Debug mode attempts to dynamically set the error_reporting and display_errors php settings). Your host may not allow this. If it works, errors would be shown on the screen.

b: Edit the .htaccess to enable displaying errors
(again, your hosts may not allow this).

c: View your http error log
most hosts provide a control panel that allows you to view the logs or allows you to view them via logging in with ssh/ftp or via the control panel's file manager.
if you can't find these... or don't think you have them.. then contact your host. If your host will not tell you how to get error logs for your account, then you need to move hosts.
Follow me on twitter
Please post system information from "Extensions >> System Information" (there is a bbcode option) on all posts asking for assistance.
--------------------
If you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
User avatar
chrisbt
Dev Team Member
Dev Team Member
Posts: 204
Joined: Sun Sep 05, 2010 6:11 am

Re: 1.11.5 Upgrade problem

Post by chrisbt »

Great advice thanks Calguy. I manually turned on error_reporting and display_errors, and got to the root of the problem.

In my SitemapMadeSimple template I called the News module (incorrectly) and this was generating the error. I suspect the issue has been around for many months as I have had unexplained issues related to the sitemap module previously.

I must run with debug on more often. Thanks :)
Locked

Return to “[locked] Installation, Setup and Upgrade”