Potential backward compatibility issues in Joomla 1.7 and Joomla Platform 11.2

From Joomla! Documentation

Revision as of 20:39, 2 June 2011 by Masterchief (talk | contribs) (Added note for JDatabaseQuery)

Platform[edit]

  • JPATH_PLATFORM is now used instead of JPATH_LIBRARIES

JDatabaseQuery[edit]

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[edit]

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

JDocumentHTML[edit]

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

JDocumentRendererMessage[edit]

  • 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]

JURI[edit]

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

JLoader[edit]

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

CMS[edit]

Refernces[edit]

  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. ↑ Remove an unused paramet in JURI::buildQuery(). (GitHub)
  5. ↑ Use include_once instead of include in JLoader (GitHub)
Retrieved from "https://docs.joomla.org/index.php?title=Potential_backward_compatibility_issues_in_Joomla_1.7_and_Joomla_Platform_11.2&oldid=59205"