Actions

Difference between revisions of "Potential backward compatibility issues in Joomla 2.5 and Joomla Platform 11.4"

From Joomla! Documentation

(JRequest)
Line 15: Line 15:
  
 
== JRequest ==
 
== JRequest ==
* JRequest::_cleanArray has been removed
+
* JRequest::_cleanArray() has been removed
  
 
== JArchive ==
 
== JArchive ==

Revision as of 18:46, 10 January 2012

This documents track potential backward compatibility issues for Joomla 2.5 and Joomla Platform 11.4 which will be included in Joomla 2.5. Listed are issues which potentially breaks extensions and newly deprecated APIs. Please help making this document complete.

The base of this comparison is Joomla 1.7/Platform 11.2.

Backwards compatibility issues were also tracked for Joomla 1.7: Potential backward compatibility issues in Joomla 1.7 and Joomla Platform 11.1

Contents

Platform

JFTP

  • All class members except JFTP::$instances have become private

JError

  • JError::$_error has become protected

JRequest

  • JRequest::_cleanArray() has been removed

JArchive

  • The following class member have become private:
    • JArchiveGzip:: $_flags
    • JArchiveGzip:: $_data
    • JArchiveTar:: $_types
    • JArchiveTar:: $_flags
    • JArchiveTar:: $_data
    • JArchiveTar:: $_metadata
    • JArchiveZip:: $_methods
    • JArchiveZip:: $_ctrlDirHeader
    • JArchiveZip:: $_ctrlDirEnd
    • JArchiveZip:: $_fileHeader
    • JArchiveZip:: $_data

JSimpleXML

  • The following class members have become private:
    • JSimpleXML:: $_parser
    • JSimpleXML:: $_xml
    • JSimpleXML:: $_stack

JComponentHelper

  • In JComponentHelper::renderComponent the execution of the component is moved to the new function JComponentHelper::executeComponent. This means that a component cannot change or use any of the (internal) variables of renderComponent that might be used by the function later on, like $task or $option. Solution is to get the values, via JRequest, in the component itself.

CMS

Plug-in events

  • onPrepareUserProfileData has been removed. Instead respond to onContentPrepareData with a context of com_users.profile