Answer for Users:
If you are getting this error because you are using some extension that sends emails, please visit the developer page, and first make sure you are using the latest version.
If you are 100% sure that you are using the latest version, but still getting this error, you should contact the developer and ask them about this error. Sending them ...
Found the issue in my own custom component...ugh. I couldn't find the offending code because I was looking for JHtmlBehavior::mootools.
But the offending code was this:
Changing it to this fixes the problem:
Simple answer is no.
Extended answer is mysql can log queries, however it has limits, and if there is even one difference between the environments it would lead to those queries not functioning. Even with that the only way to do it is though the server itself, since as far as I am aware there is no special logging added to JDatabase (Also if a component ...
mysites.guru (formerly myjoomla.com) does everything you are asking for:
✔ manage Joomla websites at different versions centrally for
✔ update Joomla
✔ update extensions
plus a great deal more:
✔ scan for malware
✔ restore compromised core Joomla files back to the original files
✔ automate backups
✔ uptime monitoring and alerts
New features ...
Answer for Joomla! users
Well, that is not a very simple one to answer, and others have already tried to explain.Namely:
GitHub Issue #9544
Similar post in Joomla.StackExchange.com
Joomla Forum Related Post
What actually happened is that some details of the default captcha included in Joomla changed, and custom form developers that do not use a certain ...
Finally I found the solution for this Error by passing the object of DateTimeZone as a parameter (notice the $date->setTimezone(new DateTimeZone($tz)); in the code bellow). It's working fine.
if($date === null )
$date = JFactory::getDate();
$tz = JFactory::getConfig()->get( 'offset' );
$date->setTimezone(new DateTimeZone($tz)); //here!
Well, a quick look inside the templates folder of the site, presented me the ugly truth - it seems that whoever did the upgrade, has never considered to clean up the site from old code/extensions/templates that are incompatible with Joomla 3.
So, in the templates folder I found 8 old templates since Joomla 1.5, that were still considered as installed ...
I know this doesn't answer all of your points but for me I have multiple sites all running 3.x
I use Akeeba, which notifies me of updates available, and is set up to create system restore points (basically SQL backups) when Joomla updates. So my routine is:
Backup every site
Check for updates to backup extensions
If there are updates for the above run ...
Go to Components>Joomla! Update
Click the Options icon in the upper right corner
If it's on Long Term Support, switch it to Short Term Support and save
See if that makes the 3.3.X update show up.
I believe it's a safe guard so you don't accidentally bump a site to 3.x without thinking about it first.
I had this issue a long time ago too. I cleared and purged all available caches, tried again and it worked. You do have an alternative which is download the update package:
Once done, install it as you would any other extension via the Extension Manager in the Joomla backend. Please remember to take a backup of your 2....
There was a similar question a couple of months ago, and the user ended up starting over with a fresh installation of Joomla.
However, this might not be an option depending on how much work you've put into the site.
Although it's hard to give a definite solution, here's a couple of things you can try:
If you're using .htaccess, try renaming it temporarily....
First, go to PhpMyAdmin, open the #__users table and check that the usertype columns exists.
If it doesn't exist then Create a new column and call it usertype.
If it does exist, then follow these steps:
Download the Update Package manually from here
Extract it to your desktop, then open the following file administrator/components/com_admin/sql/updates/...
I had the same problem recently. What helped was:
In administrator/components/com-admin/sql/updates, delete all the sql files for versions older than the start version (in my case I was updating from 2.5.28, so I deleted everything with an older version number.
Then I entered /administrator/index.php?option=com_installer&task=database.fix
This got the ...
Databases tends to be a big problem with all software development. Keeping things synced as a major pain for us too especially with staging and production sites.
One thing I have started to look at lately but not yet implemented is:
Another 'poor mans way' is to export the DB schemas (if you're concerned for schemas, data is probably a ...
Quick Dirty Method:
Take a backup of your Joomla 3.4.3 site and set it up on your localhost. Once done, download the Joomla 3.4.1 Update Package and extract it in the root directory. Don't worry about Database changes as there haven't been any since 3.4.0.
Install a fresh copy of Joomla 3.4.1
Re-download and install all 3rd party extensions
Apparently there area couple of issues with Joomla 3.5.0, one being to do with the session.
Joomla 3.5.1 will be released tonight, hopefully fixing your issue.
It may be an idea to put your site offline for a couple of hours until the update is released. And in future, I'd recommend taking a backup of your site and testing Joomla updates locally before ...
The answer probably depends on what sort of information is stored on the intranet and whether the employees and contractors who have access to the intranet are competent and can be trusted.
Is it possible that an employee or contractor could connect a compromised laptop to the internal network where malware on the laptop could compromise the ...
I have faced the very same problem many, many times. In the meantime I have learned that one can force browser to clear its cache only by versioning assets loading. So you need to find where your template loads its CSS files, and to add at the very end of loading command some type of versioning string, something like "?v=xxx". Once the browser caches ...
You can use mediaVersion. There are a few ways to do that.
Look into those 2:
Manually adding version to loaded files:
$v = JFactory::getDocument()->getMediaVersion()
JHtml versioning of loaded files:
// Add script
JHtml::_('script', 'xxx.js', array('version' => 'auto'));
// Add Stylesheets
JHtml::_('stylesheet', 'xxx.css', array('version' => '...
I'm managing 30 Joomla sites some of them are 2.5 some 3.2.
On patch I do the following per Installation:
Run a script that makes a copy to a working directory of the files
Copy the database with the current data as postfix
Switch the working directory version to the new database.
let run Joomla update on it, maybe update some other extensions
test website ...
I don't suppose you've looked at Watchful.li yet? We manage 200+ sites on a regular basis with extension and joomla updates. Watchful is designed to help manage this exact scenario pretty well. It's a newer service and they're regularly adding new features.
Out of your listed requirements, Watchful.li does all the things you want:
1) Automated Updates via ...
Although MooTools is deprecated in Joomla 3, it's still available (but might be removed in future versions).
You can load the framework by adding
(or if you need both Core and More libraries):
to your template's index.php file.
This will at least be a temporary fix, until you find ...
The best tool I have come accross for this is the SP Transfer from SP Cyend
This allows you to create a new install, get it running with appropriate template and components and then pull data accross table by table if you want.
Use it on most of our migrations, rock solid.
What I would recommend is updating as many of your key components to their latest ...
I think you might want to go first to 2.5 and then to 3.0. How to do this manually was already suggested in this question: https://stackoverflow.com/questions/19019708/joomla-1-7-5-to-2-5-migration-when-not-showing-any-updates-about-2-5
Joomla doc has also an upgrade guide: http://docs.joomla.org/J3.2:Upgrading_from_an_existing_version
I thought I would extend on Bakual's answer.
What is the Refresh Manifest Cache?
According to https://www.akeebabackup.com/support/admin-tools/15271-refresh-manifest-cache-failed.html
it detects database errors and fixes them. It's for when the update
What's causing it? How can I fix it?
Login to Joomla Admin. Go into Extension ...
The manifest cache is a field in the #__extensions table which holds the informations from the extension manifest file (the xml file describing the extension and what to install).
You can refresh it as well in the extension manager using the refresh cache button.
I don't know where the error is coming from, otherwise I would fix it :-)
I'd say it's safe. The ...
Finally able to upgrade site from Joomla 2.5.15 to Joomla 3.3.6
the upgrade work like below.
Started with Joomla 2.5.15 -> J 2.5.17 -> J 2.5.27 -> J 3.0.0 -> J 3.0.1
The Detailed Challenge and Solution can be found on Joomla Upgrade 2.5.x to Joomla 3.x.
thanks to lodder for giving the hint of Sql file! that drive me to manual upgrade.