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

From Joomla! Documentation

(Added note for JDatabaseQuery)
Line 1: Line 1:
 
= Platform =  
 
= Platform =  
 
*JPATH_PLATFORM is now used instead of JPATH_LIBRARIES
 
*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 <code>$db->getQuery(true);</code> to instantiate a query as is the '''correct''' practice in Joomla 1.6.
  
 
== JDocument ==
 
== JDocument ==

Revision as of 19:39, 2 June 2011

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]