• twitter image
  • facebook image
  • youtube image
  • linkedin image
Language: CMS Made Simple Czech CMS Made Simple France CMS Made Simple Spain CMS Made Simple Hungary CMS Made Simple Russia CMS Made Simple Netherlands

All times are UTC




Post new topic Reply to topic  [ 4 posts ] 
Author Message
 Post subject: CMSMS 1.11 - What we broke
PostPosted: Wed Jun 27, 2012 5:29 pm 
Offline
Power Poster
Power Poster
User avatar

Joined: Tue Oct 19, 2004 6:44 pm
Posts: 8169
Location: Fernie British Columbia, Canada
Here is a list of known issues that people may have with upgrading. We will endeavour to keep this list up to date throughout the beta process. And if necessary afterwards.

a: Admin Themes
- Some custom admin themes may work, but may have problems with the tooltips displayed in the content list. Changing to the NCleanGrey or OneEleven themes should solve this.

b: Smarty Templates when Caching is enabled
- Smarty templates that assign the output of a plugin to a smarty variable for later use may have problems when page caching is enabled.
i.e: {content assign='mycontent'} .... {$mycontent}
This is easily fixable by changing the {$mycontent} tag to {$mycontent nocache}

c: Modules that export content types
- We have made some significant adjustments to the main content page classes, therefore there is a danger that some modules that export content types may be effected. Hopefully these modules will be tested and/or updated in the beta process, but you should be aware that this is a concern.

d: $config['process_whole_template']
- We have removed the option to allow templates to be processed in in their entirety. Therefore, any sites that depend on this functionality may need adjustment. There is at least one third party addon module that depends on this functionality as well.

e: Postgress
- As discussed previously, this version of CMSMS no longer supports postgress.
(as a side note, the 1.11 series is the last series of CMSMS that will support PHP
5.2).

Have fun with CMSMS!

_________________
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.


Top
  Profile  
 
Share On:
Share on Facebook Share on Twitter Share on Google+
 Post subject: Re: CMSMS 1.11 - What we broke
PostPosted: Sat Jul 07, 2012 4:31 pm 
Offline
Power Poster
Power Poster
User avatar

Joined: Tue Oct 19, 2004 6:44 pm
Posts: 8169
Location: Fernie British Columbia, Canada
Addendum:

Due to circumstances beyond our control, plugins who's name ends in 'close' will fail to be recognized by smarty3. They will have to be renamed, and templates using these plugins updated.

Sorry for the inconvenience, but this was something beyond our control.

_________________
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.


Top
  Profile  
 
Share On:
Share on Facebook Share on Twitter Share on Google+
 Post subject: Re: CMSMS 1.11 - What we broke
PostPosted: Sun Jul 15, 2012 4:21 pm 
Offline
Power Poster
Power Poster
User avatar

Joined: Tue Oct 19, 2004 6:44 pm
Posts: 8169
Location: Fernie British Columbia, Canada
Update:

Just so we have all of the information in one place, here's a further update to what's been changed/updated/deprecated/broken in 1.11

lang parameter
The lang parameter passed to modules has been deprecated. Though it should still work for the 1.11 series, it will be removed in the 1.12 series. This is because we will not be allowing multiple languages (and therefore multiple locales) in the same request. This will make it easier for multi-language addon modules, and result in a considerable optimization.

default_encoding and admin_encoding deprecated
These config strings have been around for a while, with varying degrees of success. Now that the encoding is all contained within the NLS files, and the concept of 'one language, locale, and encoding' per request has been introduced these config parameters can be safely removed in an upcoming version.

_________________
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.


Top
  Profile  
 
Share On:
Share on Facebook Share on Twitter Share on Google+
 Post subject: Re: CMSMS 1.11 - What we broke
PostPosted: Sun Jul 15, 2012 5:55 pm 
Offline
Dev Team Member
Dev Team Member
User avatar

Joined: Wed Apr 23, 2008 7:53 am
Posts: 7719
Location: The Netherlands
After a successful upgrade you don't the NLS-files in the folder /admin/lang/ anymore.
So the files af_ZA.nls, ar_AR.nls, ..., ..., zh_TW.nls can be removed.

grtz. Rolf

_________________
$1

Did my post help you solving a problem at your (customers) website and it saved you many hours of work? Great!! Consider buying me a cup of coffee in return!



Top
  Profile  
 
Share On:
Share on Facebook Share on Twitter Share on Google+
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 4 posts ] 

All times are UTC


Who is online

Users browsing this forum: No registered users


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
A2 Hosting