Today, software technology firm ‘corePHP’ LLC released version 184.108.40.206, its latest version update of paGO Commerce™, e-commerce software extension built for Joomla!® CMS. You may download this latest version of paGO Commerce now for FREE on the paGO Commerce download area, here. This update includes important bug fixes and security updates. For general product information, features and benefits about paGO Commerce, go here. For further questions and support, contact ‘corePHP’ here.
Today we where informed of a SQL injection for JPhoto. After significant review of this we realized that we made a minor mistake on our part and have pushed through an early release of JPhoto. You can find out more information about the exploit here: Secunia. This version comes with a few bug fixes and some new features which will be explained in a later blog post
To upgrade simply download and install the new version of JPhoto by installing it over the current one that you have, it packaged as an upgrade. If Joomla gives you errors on installing then you have the permissions set incorrectly on your site and you will need to uninstall JPhoto and install it again, just take note of all of the configuration settings!
Thank you for using JPhoto.
This past week we have received many questions regarding the following article: http://mashable.com/2009/09/05/wordpress-please-upgrade/. It states that there is a bug going around that can affect older versions of WordPress. (The two newest releases are immune to the bug, but older versions are affected.) A lot of our users have asked if sites running WordPress for Joomla! are vulnerable and how to go about upgrading ‘corePHP’s version of WordPress to the newest release.
After a full review of the current vulnerabilities that affect WordPress, we have concluded that ‘corePHP’s distribution of WordPress is not affected because the data is handled through Joomla!.
We are currently developing the integration for version 2.8.4.
Now back to your regularly scheduled programming.
Excuse the extremely crammed title, but it stands for WordPress for Joomla! and WordPress MU for Joomla! Releases.
Unfortunately our releases do not include 2.8.x because there is still a lot of code that needs to be migrated over. However, our current releases (WP4J! 220.127.116.11 and WPMU4J! 18.104.22.168) fix a lot of bugs and add a few requested features for both extensions. This should significantly decrease the amount of support tickets you have to send in, making your job – and our job – much easier!
There is a security vulnerability on WordPress 2.8 and its previous releases. The vulnerability also affects WordPress MU 2.7.1. We have received quite a few questions about when our WordPress for Joomla! package will be updated to the latest 2.8.1. Fortunately, WordPress for Joomla! and WordPress MU for Joomla! are not affected by this vulnerability, so the security problem is not an issue.
I will be upgrading our current package (22.214.171.124) to the latest (2.8.1), and WordPress MU once 2.8.x is released.
Thank you for your patience.
Today I found a bug in Joomla! 1.5.12 while working on a project. Since I have been developing this project on my computer at home, I had it installed on Joomla 1.5.11. Yesterday I completely finished the extension and decided to test it in a different environment, so I installed a new Joomla! development site on a live server. At this point I realized that Joomla 1.5.12 had been released, so I went through the simple installation process and installed the extension I had been working on. This is where the problems started.
A few users have gotten a 500 error after installing WordPress for Joomla! and WordPress MU for Joomla! extensions. If you don’t know, a 500 Error is a server related error. I’ve been trying to figure out why this happens, and I think I’ve narrowed the issue down to a problem with the 1&1 hosting company.
Thankfully, one of the users just found a fix to this. All you have to do is put this line of code on your .htaccess file:
AddType x-mapp-php5 .php
It is as simple as that.
There is more information in 1&1 site. Our extension works on php4, but for some odd reason have to run it as php5 on the 1&1.
This bug does not affect every user, which is probably why I didn’t notice it until now. Also, it only seems to happen if you have an old version of Joomla! previous to 1.5.10.
This bug only affects the main blog when the EveryHome template is used.
If you see an error like this:
Fatal error: Class ‘JCache’ not found in /media/wpmu/themes/everyhome/home.php on line 23
The please download this file.
Rename it so it doesn’t have the .txt extension and upload it here:
We can also take care of this for you if you submit a support ticket with FTP access to your site.
The next release for WordPress MU for Joomla! is here! I have moved all of the WordPress and WordPress MU for Joomla! data and work flow into more organized systems to help speed up development and keep track of bugs, feature requests and plugin requests. After a while, post-its just don’t cut it.
We have opened up an account with LightHouse. This web service allows tracking of tickets, and we are using it to track bugs, feature requests and plugin requests for our WordPress extensions. Soon we’ll also be using it for Community ACL.
I have received multiple tickets from people who have had problems getting WordPress MU for Joomla! to use another language. I thought I tested this feature and and got it to work, but I checked again. Yes, there is a bug. Fortunately, it is still possible to get it working without waiting for a new version release.
Good news for all of our subscribers! We fixed a bug earlier this week on the component RokDownloads.
Each time a file downloaded through it, it appended all of the source code from corephp.com. WHY? Who knows…We updated to the latest version, which seems to fix this.
We apologize to those of you who had trouble installing any of the components we have (this mainly affected WordPress).
Its a great component! For more info on the component, click here.
Today I was playing around with our demo site to make sure that 2.7 worked correctly, and I found some bugs in the router file. Additionally, when I was getting ready to publish this post, someone submitted a support ticket regarding a bug that appears when Joomla is installed in a directory.