The essential news about content management systems and mobile technology. Powered by Perfect Publisher and XT Search for Algolia.
The News Site publishes posts to the following channels: Facebook, Instagram, Twitter, Telegram, Web Push, Tumblr, and Blogger.
The Joomla! Project and the Production Leadership Team are proud to announce the release of Joomla! 3.3.1. This is a maintenance release for the 3.x series of the Joomla! CMS.
If you are currently running a Joomla! release on a server with PHP 5.3.10 or later, we encourage you to update immediately to Joomla! 3.3.1 via either the one-click update or the update downloads available at https://www.joomla.org/download.html.
Note that in order to update directly to 3.3.1 via the core update component, you must be running 3.2.2 or later due to the raised minimum supported PHP version and the update system not supporting checking the server’s PHP version in older releases. Older 3.x releases will be prompted to update to 3.2.4 before being presented the 3.3.1 update....
Read more https://feeds.joomla.org/~r/JoomlaAnnouncements/~3/803XlhG3Q6k/5551-joomla-3-3-1-released.html
The Joomla Project is pleased to announce the immediate availability of Joomla 2.5.21. This is a maintenance release for the 2.5 series of the Joomla! CMS.
The update process is very simple, and complete instructions are available here. Note that there are now easier and better ways of updating than copying the files with FTP.
Note: Please read the update instructions before updating.
*Please clear your browser's cache after upgrading
Want to test drive Joomla? Try the online demo. Documentation is available for beginners.
Check the Joomla 2.5.21 Post-Release FAQs to see if there are important items and helpful hints discovered after the release.
See https://developer.joomla.org/version-2-5-21-release-notes.html for details of the tracker items fixed.
There are a variety of ways in which you can get actively involved with Joomla! It doesn't matter if you are a coder, an integrator, or merely a user of Joomla!. You can contact the Joomla! Community Development Manager,
The Joomla! Bug Squad is one of the most active teams in the Joomla! development process and is always looking for people (not just developers) that can help with sorting bug reports, coding patches and testing solutions. It’s a great way for increasing your working knowledge of Joomla!, and also a great way to meet new people from all around the world.
If you are interested, please read about us on the Joomla! Documentation Wiki and, if you wish to join, email
You can also help Joomla! development by thanking those involved in the many areas of the process. In the past year, for example, over 1,000 bugs have been fixed by the Bug Squad.
Thank you to the code contributors and active Bug Squad members that created and tested this release:
Abd Al-Mageed Suckar, Achal Aggarwal, Angel Toribio, Bastian W, Ben Tasker, Benjamin Trenkle, Bernard Saulme, Brian Teeman, Camden Narzt, Christiane Maier-Stadtherr, Chris Davenport, Christopher Masters, Daniel Sloof, David Jardin, Dennis Hermacki, Edwin Cheront, Elijah Madden, Florian Dal Fitto, George Wilson, Hannes Papenberg, Hans Kuijpers, Håvard Kristoffersen, Izhar Aazmi, Jean-Marie Simonet, Jelle Kok, Jisse Reitsma, Juelis Junior, Jurian Even, Klas Berlič, Kristijan Zivcec, Leo Lammerink, Marcel van Beelen, Marco Richter, Matt Thomas, Michael Babker, Nha Bui, Nicholas Dionysopoulos, Nick Savov, Niels van der Veer, Ove Eriksson, Ozan Ozkan, Patrick Alt, Peter Lose, Peter van Westen, Peter Wiseman, Piotr Mocko, Pruteanu Alexandru, Richard McDaniel, Robert Deutz, Roberto Segura, Roelf Pringle, Roland Dalmulder, Sebastien Heraud, Sergey Gribinichenko, Sergio Manzi, Seyi Awofadeju, Simon Asika, Stefania Gaianigo, Stefano Storti, Thomas Hunziker, Thomas Jackson, Tobias Zulauf, Todor Iliev, Valentin Despa, Viktor Vogel.
Thank you to the Joomla! Bug Squad for their dedicated efforts investigating reports, fixing problems, and applying patches to Joomla. If you find a bug in Joomla!, please report it on the Joomla! CMS Issue Tracker.
Active members of the Joomla! Bug Squad during past 3 months include: Achal Aggarwal, Andrea Zagli, Anibal Sanchez, Beat , Benjamin Trenkle, Brad Markle, Brian Teeman, Chris Davenport, Christiane Maier-Stadtherr, Dan Walker, David Jardin, Demis Palma, Dennis Hermacki, Dimitris Grammatikos, Elijah Madden, George Wilson, Hans Kuijpers, Hugo Avila, Itamar Elharar, Jean-Marie Simonet, jelle kok, Jurian Even, Lara Petersen, Leo Lammerink, Marc Antoine Thevenet, Marcel van Beelen, Marco Richter, Matt Thomas, Michael Babker, Mikhail M, Mohamed Infaz, Nick Savov, Niels van der Veer, Peter Lose, Peter Martin, Peter Wiseman, Piotr Mocko, Robert Gastaud, Roberto Segura, Roland Dalmulder, Sander Potjer, Sergio Manzi, Stefania Gaianigo, Thomas Hunziker, Thomas Jackson, Tobias Zulauf, Todor Iliev, Tom Hutchison, Valentin Despa, Viktor Vogel.
Bug Squad Leadership: Mark Dexter and Nick Savov, Co-Coordinators.
A big thanks to the Joomla! Security Strike Team for their ongoing work to keep Joomla! secure. Members include: Airton Torres, Alan Langford, Beat, Bill Richardson, Claire Mandville, David Hurley, Don Gilbert, Gary Brooks, Jason Kendall, Javier Gomez, Jean-Marie Simonet, Marijke Stuivenberg, Mark Boos, Mark Dexter, Matias Griese, Michael Babker, Nick Savov, Pushapraj Sharma, Roberto Segura, Rouven Weßling, Thomas Hunziker....
Read more https://feeds.joomla.org/~r/JoomlaAnnouncements/~3/HEp3DrKDIB8/5550-joomla-2-5-21-released.html
Read more https://feeds.joomla.org/~r/JoomlaExtensionsUpdated/~3/69sgUfBK3OA/19125
Hello!
This is informative Blog for Sorting Nested List using jQuery.
If you want to sort elements of UL/LI in another UL/LI using drag and drop, Here is a quick guide to achieve that.
Here is the basic html for nested list:
<div class="div-containing-list" > <ul id="main-list" class="main-list"> <li id="sortable1" class="connectedSortable"><span>Item 1</span> <ul class="internal-list ui-state-default"> <li class="">lesson1</li> <li class="">lesson2</li> <li class="">lesson3</li> </ul> </li> <li id="sortable2" class="connectedSortable"><span>Item 2</span> <ul class="internal-list ui-state-default"> <li class="">lesson4</li> <li class="">lesson5</li> </ul> </li> </ul> </div>
jQuery needed to achieve the drag and drop functionality
<link rel="stylesheet" href="//code.jquery.com/ui/1.10.4/themes/smoothness/jquery-ui.css"> <script src="//code.jquery.com/jquery-1.10.2.js"></script> <script src="//code.jquery.com/ui/1.10.4/jquery-ui.js"></script> <link rel="stylesheet" href="https://d1zflb13a857us.cloudfront.net/resources/demos/style.css"> <script> $(function() { //use for sorting and accordion $( "#main-list .internal-list" ).sortable(); $( "#main-list .internal-list" ).disableSelection(); $( "#main-list" ).accordion(); collapsible: true var $tab_items = $( "#main-list li" ).droppable({ accept: ".connectedSortable li", hoverClass: "ui-state-hover", drop: function( event, ui ) { var $item = $( this ); var $list = $($item.find(".internal-list" )); ui.draggable.hide( "slow", function() { $( this ).appendTo( $list ).show( "slow" ); $("#main-list").accordion({ collapsible: true, active: false }); $( $list ).parent().accordion(); }); } }); }); </script>
The output for the list is as below. Her you can drag and drop each element in the list. Chapter can be drag and drop from Section 1 to Section2 and vise versa.
Hope this blog will be help!
Read more https://techjoomla.com/beyond-joomla/sorting-for-nested-list-using-jquery.html
If you have thought of an updating facility within your website, this blog will guide you to create an update server for Joomla's update system.
A. Create or Edit an update stream
Goto your Akeeba Release System's control panel, you will find the Update stream logo.
Update stream is a relationship between the extension release inside the specified category.
Stream Name : A name for the update stream. It can be anything you want and is only used in the Joomla! 1.6 XML format streams.
Note : This is what Joomla! will also display in the Extension Name when it lists new available updates.
Alias : Used to construct the URL in the front-end. Keep it short and sweet.
Extension type : This is what type of your extension.
Category : The category where we're going to look for updates.
Package naming pattern : An update stream looks for files following a specific naming convention. You need to provide a filename and use a single question mark (?) to match any single character or a single start (*) to match any number of characters. Only items whose File or URL field matches this pattern will be included in the update stream.
For instance, if installation packages are named com_example-VERSIONNUMBER-core.zip, where only VERSIONNUMBER changes, i.e. com_example-3.1-core.zip, com_example-3.1.5-core.zip etc. This leads us to a naming pattern of com_example-*-core.zip .
Element : This is required for Joomla! 1.6 update streams. It should contain the name of your extension, e.g. com_something, mod_something, plg_something etc.
Site area (client_id) : All update streams must indicate the site area (frontend or backend) the extension applies to. Forcomponent, library and file extensions you must always use "Backend". For plugins, modules and templates select "Frontend" or "Backend" depending on whether your extension applies to the frontend or the backend of your clients' sites respectively.
Folder (for plugins) : For all extension types except plugins, leave this blank. For plugins, this must be set to the plugin type. For example, if you have a system plugin, type insystem in this box. If you have a content plugin, type in content in this box.
JED Extension ID : This is optional and only needs to be entered for extensions listed in the Joomla! Extensions Directory (JED). This is the numeric ID of your extension as listed in the JED. This is used for the Install from Web feature integration. For more information please take a look at the Content - Akeeba Release System Latest Version plugin which contains the plumbing to actually provide the URLs you need to use for the (quite convoluted) Install from Web feature.
Published : The status of the stream, also unpublished streams result in empty pages.
B. Setup update server in your extension
This definition can be used in all Joomla! 2.5 and newer compatible extensions but is not available for templates. You can use two options for your server type; collection or extension. These will be explained in detail shortly. This code should be added to the extension manifest file, within the root "extension" element. The update server is defined as follows for each type:
<updateservers>
<server type="extension" priority="1" name="SocialAds updates"><![CDATA[https://www.example.com/index.php?option=com_ars&view=update&task=stream&format=xml&id=1&dummy=extension.xml]]></server>
</updateservers>
Allowing your user to upgrade extensions with restricted downloads
Most of us developers want to provide downloads that are not openly accessible to the public. All you have to do is to create component parameters in your component's config.xml file. If you want to use username/password pairs, add the following lines after your <params> tag:
<field name="downloadid" type="text" default="" size="30"
label="Download ID"
description ="Enter your Download ID to enable Live Updates" />
<field name="username" type="text" default="" size="30"
label="Username"
description ="Enter the username to our site in order to enable Live Updates" />
<field name="password" type="text" default="" size="30"
label="Password"
description ="Enter the password to our site in order to enable Live Updates" />
Finally you can check for update by going to Extension Manager -> Update
Read more https://techjoomla.com/joomla-development/setting-up-update-streams-with-ars.html
Page 773 of 1310