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.2.4 and 3.3, the latest releases of the 3.x release series.
If you are currently running Joomla! 3.2 on a server with PHP 5.3.10 or later, we encourage you to update immediately to Joomla! 3.3 via either the one-click update or the update downloads available at https://www.joomla.org/download.html. For sites on servers with a version of PHP lesser than 5.3.10, 3.2.4 is the release for you. For other versions of the 3.x series, applying the update is recommended as soon as possible.
Note that in order to update directly to 3.3 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 update....
Read more https://feeds.joomla.org/~r/JoomlaAnnouncements/~3/p9EaFZbHrGI/5546-joomla-3-3-0-released.html
The Joomla Project is pleased to announce the immediate availability of Joomla 2.5.20.
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.20 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-20-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:
Achal Aggarwal, Allessandro Rossi, Alexandru Pruteanu, Andrea Zagli, Andrew Nester, Anibal Sanchez, Brad Markle, Brian Teeman, Carles Serrats, Chris Davenport, Constantin Romankiewicz, Dan Walker, David Hjelm, David Jardin, Demis Palma, Denise McLaurin, Dimitris Grammatikos, Edwin Cheront, Elijah Madden, Fiona Coulter, George Wilson, Hannes Papenberg, Hugo Avila, Itamar Elharar, Javier Gomez, Jean-Marie Simonet, Jurian Even, Kshitij Sharma, Lara Petersen, Marc Antoine Thevenet, Marco Richter, Mark Dexter, Marko Đedović, Matt Thomas, Michael Babker, Mohamed Infaz, Nikolai Plath, Peter Lose, Peter Martin, R Rajoz, René Alain Erichsen, Reinhard Hiebl, Robert Gastaud, Roberto Segura, Roland Dalmulder, Sander Potjer, Sebastian Hopfe, Stefania Gaianigo, Simon Asika, Thomas Hunziker, Tino Brackebusch, Tobias Zulauf, 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, Adam Przybylski, Alexandru Pruteanu, Andrea Zagli, Andrew Nester, Anibal Sanchez, Ben Charlton, Ben Griffin, Benjamin Trenkle, Brad Markle, Brian Teeman, Chris Davenport, Christiane Maier-Stadtherr, Constantin Romankiewicz, Cyril Rezé, Dan Walker, Daniel Dimitrov, David Jardin, Demis Palma, Denise McLaurin, Dennis Hermacki, Dimitris Grammatikos, Edwin Cheront, Elijah Madden, Fedik Zinchuk, Gary Mort, George Wilson, Hannes Papenberg, Hugo Avila, Itamar Elharar, Jean-Marie Simonet, Jurian Even, Kevin Griffiths, Lara Petersen, Marc Antoine Thevenet, Marco Richter, Marko Đedović, Matias Aguirre, Matt Thomas, Michael Babker, Mohamed Infaz, Nikolai Plath, Peter Lose, Peter Martin, Peter van Westen, Peter Wiseman, Piotr Mocko, Robert Deutz, Robert Gastaud, Roberto Segura, Roland Dalmulder, Sander Potjer, Stefania Gaianigo, Thomas Hunziker, Tino Brackebusch, Tobias Zulauf, Todor Iliev, Toivo Talikka, 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/DYEdhBo273E/5545-joomla-2-5-20-released.html
LinkedIn has recently updated their application requirements and needs additional information about your site if you are using the authentication features of JFBConnect for Joomla social networking[1]. The JFBConnect - LinkedIn Application setup guide[2] has already been updated with these new settings. However, if you configured your application before the last few weeks, it's likely your Application is incorrect and LinkedIn authentication may break in the future. Please take the time to follow the steps below to verify your LinkedIn Application settings and ensure authentication using JFBConnect will continue to operate smoothly.
The updated requirement is to properly configure your "OAuth 2.0 Redirect URLs" setting. If you've already configured Google+ authentication[3] on your site, this step may be familiar to you. This setting lets LinkedIn know all of the valid URLs that a user can be redirected back to on your site. This enhances security of your application by preventing some attempts at 'hijacking' the authentication request.
The steps every Joomla site user with LinkedIn authentication using JFBConnect should take are:
index.php?option=com_jfbconnect&task=authenticate.callback&provider=linkedin
https://domain.com/index.php?option=com_jfbconnect&task=authenticate.callback&provider=linkedin, https://domain.com/index.php?option=com_jfbconnect&task=authenticate.callback&provider=linkedin, https://www.domain.com/index.php?option=com_jfbconnect&task=authenticate.callback&provider=linkedin, https://www.domain.com/index.php?option=com_jfbconnect&task=authenticate.callback&provider=linkedin
Please note: That setting should be a comma-separated list and all be on one line without line breaks after each value/comma. It will be hard to read, but that's how LinkedIn's settings work.
We have submitted a question to LinkedIn about a method to make the setting less complex (by not using the query string), but until that's answered, the solution above is the option we'd recommend. Until they enforce this new requirement, it's not possible for us to guarantee everything will work, but we are monitoring the update and will keep you posted of any new information we find.
As always, comments and feedback are welcome!
Read more https://www.sourcecoast.com/blog/linkedin-please-verify-your-application-settings
I noticed npm’s blog had a post about who’s hiring in the Node community. There’s a new Who’s Hiring page on npmjs.org, that lists Voxer, The Financial Times, Branding Brand, and Dash.
More people are getting interested in Koa.js now, so it’s good to start collecting example applications that use it. Ramesh Nair sent in Melkor (License: MIT), a wiki that uses Waigo which is built on Koa.js, and Git as the storage system.
You can see generators used right away in index.js
:
exports.init = function*(folder, options) {
debug('Folder: ' + folder);
yield* waigo.init({
appFolder: path.join(__dirname, 'src')
});
var App = waigo.load('application');
yield* App.start({
postConfig: function(config) {
config.startupSteps.unshift('wiki');
config.middleware.push({ id: 'methodOverride' });
debug('Port: ' + config.port);
config.port = options.port;
config.baseURL = 'https://localhost:' + config.port;
config.staticResources.folder = '../public/build';
config.wikiTitle = options.title;
config.wikiFolder = folder;
}
});
return App;
};
The controllers also make heavy use of yield
, so things like form validation and template rendering have a synchronous feel.
Isosurface (GitHub: mikolalysenko / isosurface, License: MIT, npm: isosurface) by Mikola Lysenko is a set of isosurface polygonizer algorithms.
Here’s an example:
var isosurface = require('isosurface');
var mesh = isosurface.surfaceNets([64,64,64], function(x,y,z) {
return x*x + y*y + z*z - 100;
}, [[-11,-11,-11], [11,11,11]]);
I found this module (and the impressive demo) while looking through Mikola’s graphics related modules on npmjs.org/~mikolalysenko.
Read more https://feedproxy.google.com/~r/dailyjs/~3/X9hyklwTvGg/node-roundup
Our main focus with Magento lies with our bridge with Joomla! (MageBridge) and performance tuning. But over the years, we have developed numerous Magento sites and have bumped into little annoyances - shortcomings in Magento. To solve our own issues, we developed Magento extensions that are often seen as must-haves for any Magento shop. We love to share these essential Magento extensions with you.
When building a Magento site, you will also need to customize the transactional emails that are sent as part of the sales process (invoices, order confirmations, shipment notices). Customizing them requires design skills, but by default, testing these emails is a lenghty job: It requires creating an order for every combination of products you want to preview (so running through the entire checkout), something you definitely do not want to do that often.
Our EmailTester[1] extension is a life-saver: It allows you to quickly preview any email in your browser or email client - complete with live data (order, invoice, customer, product) of your choice. This extension saves you tons of time when customizing emails.
Similar to the EmailTester extension, the CheckoutTester[2] extension solves an issue that would either require a lot of time ... or core hacks. If you want to customize the success-page that is shown to visitors once they have completed the checkout, you will need to create an order, run through the entire checkout - just to see what's at the last page of that process. A refresh will redirect you back to an empty cart. Impossible to use when trying to optimize the checkout.
Forums mention a core hack for this: Simply stop Magento from dropping the session and redirecting back to cart. A core hack, right. Definitely not something you want to do on your live site. Our CheckoutTester[3] extension allows you to preview the success page without core hacks and without lengthy procedures. Simply visit the preview URL and you're done. We personally find it impossible to customize the success-page on a live site without this extension!
Perhaps not something for everybody, but our DeleteAnyOrder[4] extension makes it possible to remove orders from the Magento database, complete with all their dependancies. This is perfect when having a Magento site that is not yet in production, but even better when you are already in production (if your bookkeeper does not object): Say there's an issue with your checkout, and you want to test things yourself by creating test-orders. Once you're done, you're stuck with dummy orders that do nothing except clutter up your system.
Our DeleteAnyOrder[5] extension allows you to remove all order data from the Magento database. Even better: It does so in a very secure way, preventing data corruption. There's even a complete integrity check tool in the backend that allows you to see the current status of your database. A vital tool when troubleshooting checkout failure.
When you are customizing a Magento site, you have become familiar with Magento theming and its override mechanism: You can create a parent theme and child theme, and override XML-layout files, PHTML-templates, CSS-files and images by simply copying the right file to the right folder. But with the email template-files you can't. What? Yes, you can't. The email template-files (located in app/locale/en_US/template/email) can't be copied to your theming folder.
With our EmailOverride[6] extension this shortcoming is solved. Simply install the extension, and override the email files as you wish. A very simple solution for something so fundamental, that every Magento designer bumps into this.
I asked my girlfriend to enter some products in Magento and after she worked for some time, she accidently deleted a product instead of saving it. 10 minutes of editing were gone. So she asked me if I could restore the product. I could not. Because Magento lacks the functionality of a recycle bin. My girlfriend looked at me and said I'd better create one, because a trashcan is something so fundamental that she could not believe it did not exist.
So here it is: The Yireo Trashcan[7] offers a recycle bin for all Magento users who belief that Magento behaves the same way as WordPress, Joomla!, Drupal and probably most other web applications that deal with content.
Last but not least: The Magento application is notorious for writing logs to Magento database-tables that are rarely used. Most people use external services like Piwik or Google Analytics for logging. Cleaning the Magento database-tables is therefor something that is frequently included in cronjobs. But why is the logging done in the first place? Every Magento request includes about 4 or 5 write queries to the Magento database, which are actually included there for no reason.
The Yireo DisableLog[8] extension allows you to disable the Magento logging entirely. This does not only saves a couple of microseconds from every webrequest (in short: it makes your site a little bit faster), but it also keeps the Magento database from growing out of proportions. We have already heard great comments from users who noticed performance gains thanks to our extension. There's little reason not to install it.
There you are: 6 essential Magento extensions. I hope you like them. If you have any suggestions or questions let us know.
Read more https://www.yireo.com/blog/1676-6-essential-magento-extensions
Page 792 of 1311