You do not need to un-install the free version before installing the pro version of this extension. In fact, keeping the free version will help migrate your previous configuration.
Before updating, make sure you read the change logs and are aware of potential backward compatibility issues.
Cached scripts and styles are removed on update. Updates fix issues, add features and/or improve performance and these wouldn't be reflected unless all cached files are re-generated.
Moving to Joomla 5 from Joomla 4.4
The upgrade is seamless and no side effects have been reported so far. If you have the latest version installed under Joomla 4.4, no update is necessary when upgrading to Joomla 5.
The extension works properly with or without the Compatibility plugin enabled.
Moving to Joomla 4 from Joomla 3.10
For a successful migration to Joomla 4, the extension first needs to be up to date in your Joomla 3.10 configuration.
To avoid errors on the updated site until Article Details has been re-installed, you should disable the plugin temporarily prior to the migration to Joomla 4.
There are a few changes for Article Details free and Profiles:
- The core component com_mailto has been removed from Joomla 4. This impacts the sharing of articles though emails. Email sharing will remain available through a simple mailto: link instead,
- Article printing has been removed from Joomla 4 as well. The capability will remain available in the extensions,
- jComments support has been removed,
- Features related to Community Builder are disabled temporarily,
- Profiles Template overrides for the layouts NEED to reflect the changes made for Joomla 4 compatibility. If you have created any, you must update them.
For general instructions on moving from Joomla 3.10 to Joomla 4, please check this tutorial out!
Must read: specific instructions about the migration for this extension.
Updating to v6.3 from v6.2.x
Joomla 4 The Chosen dependency for the voting system has been removed. The vote form is now part of the rating.php layout, for easier overrides. If you have an override for adp_detail_rating.php, you will need to adjust it.
Joomla 4 Web font support for Bunny.net (GDPR compliant fonts)
Migrating to v6.2 from v6.1.x
Profiles You can now show custom fields of type SQL as article information.
Migrating to v6.1 from v6.0.x
Parameters have been re-organized, and tabs renamed to make it easier to find features. Styles have their own tab now, and original details as well (where original information can be hidden from view when duplicated on the screen).
Migrating to v6.0 from v5.7.x
Profiles Joomla 4 The icon picker can now handle Font Awesome icons. They can be edited manually. However, to add this functionality, a few changes were necessary in the detail layouts. Therefore, if you have any override of detail layouts or if you have created your own layouts, you will need to update them if you show icons (even if you just show the default icons). There is also an update for the sample add-on.
Migrating to v5.7 from v5.6.x
This version brings support to the AVIF image type (PHP 8.1+). It also adds image versioning, easing testing and reducing cache issues.
Joomla 4 The extension supports the Imagick PHP image extension. If Imagick is available on your server, you may use it instead of the GD extension.
Migrating to v5.6 from v5.5.x
There are no changes impacting your configurations, most modifications are under-the-hood. However, note that the social networks Google+ and StumbleUpon have been removed.
Joomla 4 Joomla 4 versions (the free one and the pro) are not final. Please download and try. I appreciate your feedback.
Migrating to v5.5 from v5.4.x
There are no changes impacting your configurations.
Migrating to v5.4 from v5.3.x
There are no changes impacting your configurations.
Migrating to v5.3 from v5.2.x
Profiles You need to update the layout overrides to take advantage of the new features.
Migrating to v5.2 from v5.1.x
Profiles Please verify that you do not have an override for the adp_detail_share layout. If you do, you will have to modify/replace it and add the adp_detail_share new folder and its content.
Migrating to v5.1 from v5.0.x
Profiles You need to update the layout overrides to take advantage of the new extra class parameter.
- fixed shared media icons show on mobile devices with PHP mobile detection, not CSS media queries anymore
- breakpoint's default is set in the global configuration. Module instances get that value by default, not the plugin's value anymore. Plugin value needs to be empty to get global default
Migrating Article Details Profile to v5.0 from v4.2.x
The extension is now packaged as a component. It adds layout support for all article details and an information dashboard.
There is a modification in the way labels show for each article detail. From now on, if a specific label is added in the console, it has precedence over the default label. In previous versions, the default label had precedence (default labels are labels that are created through language overrides).
Migrating Article Details to v4.3 or v5.1 (Joomla 3.8+) from v4.2.x
You can safely update the plugin.
Migrating to v4.2 from v4.1.x
CSS classes info-header and info-footer have been removed, therefore if you added custom CSS using those classes, please review your code:
- replace
.info-headerwith.articledetails-header .info - replace
.info-footerwith.articledetails-footer .info
Profiles Pill
and Flip
calendars are now part of the extension. No update needed.
Migrating to v4.1 from v4.0.x
Information blocks are no longer placed inside the p HTML tag but into dl/dd tags instead.
FreeMigrating to v4.0 from v3.0.x
You can safely update the plugin but there are major differences to consider:
1 The plugin behaves differently in article list views (blogs and featured) and article views. The plugin considers them now distinct and you will need to reset a few options for lists (see the layout tab).
2 Information details classes have been re-labelled for better skinning. If you rely heavily on CSS to make changes to the standard output, you may need to make some modifications.
For instance:
<p class="details">
<span class="detail detail_tags">
<i class="SYWicon-tags"></i>
<span class="article_tags">Tags : tag 1, tag 2, tag 3</span>
</span>
</p>is now:
<p class="details">
<span class="detail detail_tags">
<i class="SYWicon-tags"></i>
<span class="detail_label">Tags : </span>
<span class="detail_data">tag 1, tag 2, tag 3</span>
</span>
</p>There are also a lot more options now to 'skin' the output and some of your CSS overrides may not be necessary anymore.
3 You need to re-select the share icons previously selected. The plugin is backward compatible with old values only until you save it again.
4 The caching of stylesheets and scripts has gone through a total rewrite. It is no longer necessary to change file permission access on websites that have very tight security rules. If you have setup file permission access for the files of this plugin, you can now safely remove them from your server configuration.
You may still, however, run into access permissions under the new caching system. In that case, it is just a matter of granting access to (or white-list
) the /cache folder created for the extension.
Migrating to v4.0 from v2.0.x
Here are the few additional changes that can affect your outputs:
5 If the parameter location was used to show the information details BEFORE the title, all information will show AFTER the title. The parameter location has been removed and replaced with sections before title and after title.
6 The language override PLG_CONTENT_ARTICLEDETAILS_APPEND_HITS has been replaced with PLG_CONTENT_ARTICLEDETAILS_HITS. Therefore, if this key has been overridden, you will need to modify it.
7 Information may disappear. The reason is: the plugin takes into account the article options and does not override them anymore.
8 The CSS that hides the original article title has been modified to accommodate the latest Joomla versions. Therefore, the title might show twice in your configuration. Correct this by changing the values of the Title parameter in the advanced tab of the plugin. In previous versions, .item-page h2 was replaced with .item-page h2:first-of-type automatically. It needs to be specified explicitly from now on to avoid confusion.
