Actions

Difference between revisions of "Potential backward compatibility issues in Joomla 1.7 and Joomla Platform 11.2"

From Joomla! Documentation

(Platform)
Line 14: Line 14:
 
=== JDocumentRendererMessage ===
 
=== JDocumentRendererMessage ===
 
*A div element with the ID "system-message-container" is always rendered, whether there are messages or not. This ID should not be used in any extension or template.<ref>[https://github.com/joomla/joomla-platform/commit/bade3acf0f5ea588be92cb24d4237228c043a3c7 Modify JDocumentRendererMessage to always render &lt;div id="system-message-container">&lt;/div>. This makes it possible to render messages via JavaScript. (GitHub)]</ref>
 
*A div element with the ID "system-message-container" is always rendered, whether there are messages or not. This ID should not be used in any extension or template.<ref>[https://github.com/joomla/joomla-platform/commit/bade3acf0f5ea588be92cb24d4237228c043a3c7 Modify JDocumentRendererMessage to always render &lt;div id="system-message-container">&lt;/div>. This makes it possible to render messages via JavaScript. (GitHub)]</ref>
 
== JURI ==
 
*The unused parameter $akey has been removed from JURI::buildQuery().<ref>[https://github.com/joomla/joomla-platform/commit/14ebbbd702c2d79098057647fcc4603157896509 Remove an unused paramet in JURI::buildQuery(). (GitHub)]</ref>
 
  
 
== JLoader ==
 
== JLoader ==
 
*JLoader can't load files multiple times anymore.<ref>[https://github.com/joomla/joomla-platform/commit/bfef02de71db7aa5cb46ffdff92778fd6f14f621 Use include_once instead of include in JLoader (GitHub)]</ref>
 
*JLoader can't load files multiple times anymore.<ref>[https://github.com/joomla/joomla-platform/commit/bfef02de71db7aa5cb46ffdff92778fd6f14f621 Use include_once instead of include in JLoader (GitHub)]</ref>
 +
 +
== JLog ==
 +
* JLog has shifted to joomla.log.log from joomla.error.log and features support for multiple loggers.
 +
 +
== JURI ==
 +
*The unused parameter $akey has been removed from JURI::buildQuery().<ref>[https://github.com/joomla/joomla-platform/commit/14ebbbd702c2d79098057647fcc4603157896509 Remove an unused paramet in JURI::buildQuery(). (GitHub)]</ref>
  
 
= CMS =
 
= CMS =

Revision as of 03:30, 4 June 2011

Contents

Platform

  • JPATH_PLATFORM is now used instead of JPATH_LIBRARIES

JDatabaseQuery

JDatabaseQuery is now abstract due of the work done to support new database engines (Windows Azure and Microsoft SQL Server). This means you must use $db->getQuery(true); to instantiate a query as is the correct practice in Joomla 1.6.

JDocument

  • getHeadData(), setHeadData() and mergeHeadData() are from now on only present in JDocumentHTML. They have been removed from JDocument and JDocumentXML.[1]

JDocumentHTML

  • JDocumentHTML::$_links has changed to a multidimensional array. Also the rendering of the link elements has been moved from JDocumentHTML to JDocumentRenderHead.[2]

JDocumentRendererMessage

  • A div element with the ID "system-message-container" is always rendered, whether there are messages or not. This ID should not be used in any extension or template.[3]

JLoader

  • JLoader can't load files multiple times anymore.[4]

JLog

  • JLog has shifted to joomla.log.log from joomla.error.log and features support for multiple loggers.

JURI

  • The unused parameter $akey has been removed from JURI::buildQuery().[5]

CMS

General Coding Principles

Within the new Joomla release cycle, developers need to be conscious of more frequent changes to version numbers. If you are doing hard checks against, for example, a version number exactly equal to "1.6" then as we move to 1.7, those checks may fail with unexpected results. You should ensure that version checks appropriately allow for future increments like 1.7, 1.8, 2.0, 3.0, and so on.

References

  1. Remove getHeadData(), setHeadData() and mergeHeadData() from JDocument since it only applies to JDocumentHTML. (GitHub)
  2. Move the rendering of HTML link elements to JDocumentRendererHead. (GitHub)
  3. Modify JDocumentRendererMessage to always render <div id="system-message-container"></div>. This makes it possible to render messages via JavaScript. (GitHub)
  4. Use include_once instead of include in JLoader (GitHub)
  5. Remove an unused paramet in JURI::buildQuery(). (GitHub)