What this is:
If you are seeing this message:
the CMS is put in a state where it will no longer accept software updates. Since sometimes fixing problems in the CMS require a new build of the software, we will be unable to make changes or fixes to the software until the system is in a state where it can be updated again.
If you are using a version before 4.0.5701 or after 4.0.5790
If you are seeing this message, please submit a ticket to support and we will let you know why this is the case and what can be done to get you on a version that is back on a version with support.
If you are using a version of the software between 4.0.5701 and 4.0.5790
If you are seeing this message and are on a version of the software that is 4.0.5701 or greater, but under 4.0.5790, we put your software in this state because we detected that your software is using custom templates that will break in the new build.
Here are changes to the software that may cause breakage in your custom templates.
websiteid
Our system no longer uses the websiteid column in any of its tables. Newer versions of the software have specifically removed the ability for separate Site Ids to share the same database. We removed this to help with database size and system performance.
While none of our templates directly connect to the database, custom developers who did not use our PHP API were specifically referencing this column in some of their code. One way to find this code is for your host to do the following from the /cms_admin/ folder:
fgrep -Ri "websiteid" phptemplate/
Here is some example results:
phptemplate/site_custom1/functions/standard.tpl: $sql='SELECT * FROM plg_tour_contentgroup WHERE TourId = "'.$tour_ID.'" AND websiteid="0" AND contentgroup = "'.$set_ID.'" LIMIT 1';
phptemplate/site_custom1/functions/standard.tpl:function custom_get_category_tags($websiteid = 0, $subsite_id = 'all'){
phptemplate/site_custom1/functions/standard.tpl: $sql='SELECT * FROM category WHERE websiteid = "'.$websiteid.'" AND Parent="3" ORDER BY Title ASC';
phptemplate/site_custom1/index.tpl: <?php $tags = custom_get_category_tags($root['area']['websiteid'], $root['subsiteid']); ?>
phptemplate/site_custom1/index.tpl: <?php $tags = custom_get_category_tags($root['area']['websiteid'], $root['subsiteid']); ?>
phptemplate/site_custom2/functions/standard.tpl: $sql='SELECT * FROM plg_tour_contentgroup WHERE TourId = "'.$tour_ID.'" AND websiteid="0" AND contentgroup = "'.$set_ID.'" LIMIT 1';
phptemplate/site_custom2/functions/standard.tpl:function custom_get_category_tags($websiteid = 0, $subsite_id = 'all'){
phptemplate/site_custom2/functions/standard.tpl:function old_custom_get_category_tags($websiteid = 0, $subsite_id = 'all'){
phptemplate/site_custom2/functions/standard.tpl: $sql='SELECT * FROM category WHERE websiteid = "'.$websiteid.'" AND Parent="3" ORDER BY Title ASC';
phptemplate/site_custom2/index.tpl: <?php $tags = custom_get_category_tags($root['area']['websiteid'], $root['subsiteid']); ?>
phptemplate/site_custom2/index.tpl: <?php $tags = custom_get_category_tags($root['area']['websiteid'], $root['subsiteid']); ?>
phptemplate/site_custom3/functions/standard.tpl: $sql='SELECT * FROM plg_tour_contentgroup WHERE TourId = "'.$tour_ID.'" AND websiteid="0" AND contentgroup = "'.$set_ID.'" LIMIT 1';
phptemplate/site_custom3/functions/standard.tpl:function custom_get_category_tags($websiteid = 0, $subsite_id = 'all'){
phptemplate/site_custom3/functions/standard.tpl: $sql='SELECT * FROM category WHERE websiteid = "'.$websiteid.'" AND Parent="3" ORDER BY Title ASC';
When you see statements like SELECT, these are SQL statements. This means that the template code is connecting to the database directly. Since it will no longer find the websiteid column in newer versions of the sofware, these queries will fail and cause site disruption.
Here are some options on what you can do here:
- Best: Consider switching over to the PHP Templating API. This is a stable API that will not break if we do under the hood database changes. If you are using a contract developer, they may already have replacement functions that use our templating API.
- Good: Contact your developer. If they have done contract work for your site, there is a good chance that they have an updated version of these files that do not reference this.
- OK: We can go through and remove instances of websiteid within your templates. If you wish to go this route, please submit a ticket. Keep in mind that there may be a waiting list for this.
The following columns have also been removed from the system:
While all of these fields mostly refer to unused, empty columns from the XSL template system, your developer can do an audit to make sure these columns are not being retrieved directly.
PreviewXML - This was used in the XSL templating language, which has been discontinued. For metadata, look at the PreviewXML_PHP or info columns.
category.PreviewXML
contentgroup.PreviewXML
plg_bonus.PreviewXML
plg_contentasc.PreviewXML
plg_dvdasc.PreviewXML
extrafields - This was used in the XSL templating language, which has been discontinued. For metadata, look at the extrafields_PHP or extrafields_PH2 columns.
category.extrafields
plg_contentasc.extrafields
contentgroup.extrafields
Other fields:
content.Files - This was used in the XSL templating language, which has been discontinued. For metadata, look at the Files_PHP columns.
content.AppearDate - Individual content within a scene no longer has its own release date. Please use contentgroup.AppearDate instead.content.DaysVis - Individual content within a scene no longer has its own release date. Please use contentgroup.AppearDate instead.
contentgroup.AppearUpd - This was an unused column.
plg_tour.LastRebuild - Static build tours are no longer supported.
plg_tour.RebuildFreq - Static build tours are no longer supported.
