Actions

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

From Joomla! Documentation

(CMS)
m (changed framework category to platform category as platform category exists)
(6 intermediate revisions by 4 users not shown)
Line 1: Line 1:
This documents track potential backward compatibility issues for Joomla 2.5 and Joomla Platform 11.4 which is included in Joomla 2.5. Listed are issues which potentially break extensions and newly deprecated APIs.
+
{{RightTOC}}This documents track potential backward compatibility issues for Joomla 2.5 and Joomla Platform 11.4 which is included in Joomla 2.5. Listed are issues which potentially break extensions and newly deprecated APIs.
 
Please help making this document complete.
 
Please help making this document complete.
  
Line 6: Line 6:
 
Backwards compatibility issues were also tracked for Joomla 1.7: [[Potential backward compatibility issues in Joomla 1.7 and Joomla Platform 11.1]]
 
Backwards compatibility issues were also tracked for Joomla 1.7: [[Potential backward compatibility issues in Joomla 1.7 and Joomla Platform 11.1]]
  
= Platform =
+
= CMS Libraries and Platform Version=
  
 
== JFTP ==
 
== JFTP ==
Line 42: Line 42:
 
== Plug-in events ==
 
== Plug-in events ==
 
*onPrepareUserProfileData has been removed. Instead respond to onContentPrepareData with a context of com_users.profile
 
*onPrepareUserProfileData has been removed. Instead respond to onContentPrepareData with a context of com_users.profile
 +
 +
== JUser ==
 +
The Associative array of user groups for a user no longer contains the group name, but only the group id in both the key and value.
 +
The names of groups for a user can be obtained from getGroupsByUser in JAccess.
  
 
= CMS =
 
= CMS =
== Updater for Plugins ==
+
== Plugin Extension Manifest for Update Servers ==
(as of 1.7.3) Your xml updater must specify the client <client>0</client> in the <update> sections. Example:
+
(as of 1.7.3) The xml extension manifest for plugins on update servers must specify the client <client>0</client> in the <update> sections. Example:
 +
 
 +
<type>plugin</type>
 +
<folder>content</folder>
 +
<client>0</client>
  
<type>plugin</type>
+
[[Category:Compatibility]]
<folder>content</folder>
+
[[Category:Development]]
<client>0</client>
+
[[Category:Platform]]

Revision as of 13:13, 29 August 2012

Contents

This documents track potential backward compatibility issues for Joomla 2.5 and Joomla Platform 11.4 which is included in Joomla 2.5. Listed are issues which potentially break 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

CMS Libraries and Platform Version

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.

Plug-in events

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

JUser

The Associative array of user groups for a user no longer contains the group name, but only the group id in both the key and value. The names of groups for a user can be obtained from getGroupsByUser in JAccess.

CMS

Plugin Extension Manifest for Update Servers

(as of 1.7.3) The xml extension manifest for plugins on update servers must specify the client <client>0</client> in the <update> sections. Example:

<type>plugin</type>
<folder>content</folder>
<client>0</client>