Actions

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

From Joomla! Documentation

(Add todays merges from GitHub)
Line 1: Line 1:
= Platform =  
+
This documents track potential backward compatibility issues for Joomla 1.7 and Joomla Platform 11.1 which will be included in Joomla 1.7. Listed are issues which potentially breaks extensions and newly deprecated APIs.
 +
 
 +
Please help making this document complete.
 +
 
 +
= Platform {{JVer|11.1}} =  
 
*JPATH_PLATFORM is now used instead of JPATH_LIBRARIES (JPATH_LIBRARIES will continue to be supported for version 1.7)
 
*JPATH_PLATFORM is now used instead of JPATH_LIBRARIES (JPATH_LIBRARIES will continue to be supported for version 1.7)
  
Line 31: Line 35:
 
* checkAll() has been deprecated, use Joomla.checkAll() instead. Note that Joomla.checkAll() doesn't include some legacy functionality.<ref>[https://github.com/joomla/joomla-platform/commit/d9ec6d3e15344727dc7453c4cce9137b634e8b2c Namespace the checkAll() function. (GitHub)]</ref>
 
* checkAll() has been deprecated, use Joomla.checkAll() instead. Note that Joomla.checkAll() doesn't include some legacy functionality.<ref>[https://github.com/joomla/joomla-platform/commit/d9ec6d3e15344727dc7453c4cce9137b634e8b2c Namespace the checkAll() function. (GitHub)]</ref>
  
= CMS =
+
= CMS {{JVer|1.7}} =
 
== General Coding Principles ==
 
== 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.
 
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.

Revision as of 16:22, 14 June 2011

This documents track potential backward compatibility issues for Joomla 1.7 and Joomla Platform 11.1 which will be included in Joomla 1.7. Listed are issues which potentially breaks extensions and newly deprecated APIs.

Please help making this document complete.

Contents

Platform Joomla 11.1

  • JPATH_PLATFORM is now used instead of JPATH_LIBRARIES (JPATH_LIBRARIES will continue to be supported for version 1.7)

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]

JUpdater

  • JUpdater:: arrayUnique() has been deprecated Use JArrayHelper::arrayUnique() instead. Note that the later is static.[6]

JavaScript

  • MooTools Core has been updated to version 1.3.2, MooTools More to 1.3.2.1. Due to a change in JSON handling a slight change in behavior can occur. More details can be found on the MooTools Wiki.[7]
  • checkAll() has been deprecated, use Joomla.checkAll() instead. Note that Joomla.checkAll() doesn't include some legacy functionality.[8]

CMS Joomla 1.7

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.

TinyMCE

  • TinyMCE has been updated to the 3.4 series requiring new language files and potentially breaking TinyMCE plug-ins.[9]

JavaScript

  • MooTools Core and MooToools more will not always be loaded in the backend as it was in the past. Extensions have to specifically include it.[10]

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)
  6. Move JUpdater:arrayUnique() to JArrayHelper::arrayUnique(). Keep JUpdater:arrayUnique() as an alias an deprecate it. (GitHub)
  7. Update Mootools to version 1.3.2 (Issue) (Revision) (GitHub)
  8. Namespace the checkAll() function. (GitHub)
  9. Update TinyMCE to version 3.4.2 (Issue) (Revision)
  10. Don't always load Mootools (More) in the backend (Issue) (Revision)