[Solved] Add New Content section doesn't work /display

[pwg]

I recently (yesterday) upgraded from 1.10.3 to 1.11.5 and while I think all worked post upgrade, now I can add any new page content.

I can add Templates, GCB's etc, it is only the New content within Pages that isn't working.

I've uninstalled any extra modules I had, re-installed the CNMS, downloaded a new version and installed it, all to no avail.

Anyone have any ideas why?

The Add New Content page appears to be the only one affected.

I'm hoping I'm just being dim and missing something obvious.

Thanks for any help.

Cheers

Paul

[pwg]

Hi,

Further to this, I updated the site to CMSMS version 1.11.6 which made no difference - I'm still not able to add new content. all other functions seem to be working.

Site is on PHP 5.2, Appache. Was perfect prior to upgrade.

Even with this, I updated another site, which was working well, to 1.11.6 and now I can't add New content to it either. All other functions appear to be working.

Somebody must have some idea what is happening or causing the problem?

ANY help greatly appreciated.

Thanks,

Paul

[velden]

Maybe enabling the debug in config.php will help you. Anything logged in Admin log?

[Rolf]

System Information?

[psy]

It's possible something in your template is incompatible with v1.11+.

Have you tried switching to one of the cmsms-supplied templates?
Are your modules updated to be compatible with v1.11+?

Recommended minimum PHP version is 5.3+. Many modules no longer work with PHP 5.2.

On the frontend, have you tried to view source to see where it is breaking?

[pwg]

Hi, Thanks for the replies.

System info is as follows;
Cms Version: 1.11.6

Installed Modules:

CMSMailer: 5.2.1
FileManager: 1.4.3
MenuManager: 1.8.5
ModuleManager: 1.5.5
News: 2.12.12
Printing: 1.1.2
Search: 1.7.8
ThemeManager: 1.1.8
TinyMCE: 2.9.12
FormBuilder: 0.5.12
simpletagging: 0.2.1
RSS: 1.1
RSS2HTML: 1.2.5.1
Comments: 1.9.2
Album: 0.9.3
CGExtensions: 1.32.6
CGFeedMaker: 1.0.17
Play: 1.0.3
DewPlayer: 0.2.1
avplayer: 1.0
FLVPlayer: 1.0.3
Twitter: 0.0.6
Backup: 0.5
CMSPrinting: 1.0.4
MicroTiny: 1.2.5

Config Information:

php_memory_limit:
process_whole_template:
output_compression:
max_upload_size: 50000000
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.17
md5_function: On (True)
gd_version: 2
tempnam_function: On (True)
magic_quotes_runtime: Off (False)
E_STRICT: 0
E_DEPRECATED: 0
memory_limit: 64M
max_execution_time: 30
output_buffering: 4096
safe_mode: Off (False)
file_uploads: On (True)
post_max_size: 50M
upload_max_filesize: 50M
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.1.63
Server Db Grants: Found a "GRANT ALL" statement that appears to be suitable


i just brought the whole site down by trying to install CGBlog and SimpleSmarty, not sure if this is related or not.

Thanks again for any help.

Cheers,

Paul

[psy]

Nearly all CG modules now require PHP 5.3. You are running PHP 5.2

There are also a lot of old modules installed, eg FB 0.5.12. Latest version is 0.7.3

It's probable the cause of your problems are installed modules that are incompatible with cmsms 1.11+

Firstly, upgrade all modules to latest versions. If the problem persists, disable all modules then switch them back on one-by-one until you find the culprit(s).

Also check what's being reported in the Admin log.

[pwg]

Thanks again for the replies.

I've solved the issue by deleting an extra file in the plugins folder (function.sylesheet.php).

New versions have function.cms_sytlesheet.php

psy, thanks, but it is running php 5.3, however I do take your point about some of the modules. I'll be clearing them out now.

Cheers,

Paul

[psy]

Glad it's fixed.

[Dr.CSS]

Having a problem with that most times means you have {stylesheet} tag in template which needs to be {cms_stylesheet} now...