Each extension provider creates their own update server which is specified in the manifest file included with the extension. Here is the Joomla! documentation on deploying an update server.
While this sounds complicated, it is actually really simple. At it's most basic, the server consists of an XML file that tells Joomla! where to find each available ...
If you don't have Akeeba Backup installed:
Go back to the Joomla Update page
Upload and install the Joomla 3.6.1 Update Package using the "Upload & Update" tab
Go to Extensions >> Manage >> Database
You may see a message that the database is out of date. If so, click on the Fix button in the toolbar.
If you have Akeeba Backup installed:
Go to the ...
Details about this issue can now be found in the Joomla Docs:
What is the cause?
3.6.1 introduced a CSRF token check to the update component as an extra level of security. 3.6.0 down to 2.5.4 (every version with the
update component) will hit the issue with the CSRF token because those
versions don't generate the needed code to pass the check. ...
This is usually caused by the cache mechanisms in Joomla. It has nothing to do with the Joomla 2.5. eol.
Clear Cache and purge expired cache from the maintenance menu, and also it usually helps if you go to Extensions Manager -> update / manage and Clear/Refresh the cahce for the extensions there.
Then go to the Joomla Update Component and see if it ...
The updates for 3.3.5 and 2.5.26 were pulled after a last minute (but minor) issue was detected.
Please see: https://plus.google.com/+joomla/posts/XmkJAm4fCGS
As it mentions if you've already run the update (or applied it manually) it's not a problem but you ...
I think the article is not up-to-date because update server is working properly with template.
Here's the code I use in the templateDetails.xml
<server type="extension" name="mytemplate" priority="1">http://www.domain.com/updates/template.xml</server>
And this is the content of my http://www....
My version of Implementation would be...
The Client:- Just give each subscribed user a unique(secret) key and simply pass that as GET variable when checking for new updates.
The Server:- Likewise, just check the incoming requests for that variable, and match it with a database, cool? allow : deny;.
The Misuse:- Keep a record of each key being used, and ...
If I'm not mistaken, moving changes from your localhost/dev-environment to the live site should be pretty straight forward.
Before doing anything, keep a backup of your site live.
As I'm sure you're aware, all settings (apart from the global config) are stored in the database, so if you've made any HTML changes, simply copy all the directories (...
For Joomla core updates go under Components > Joomla! Update. If it does not appear the new update click on the "Clear Cache" button and all should be fixed.
Extensions > Manage > Update refers only to components/plugins/module..
Also check this article that explains how to fix the Joomla! Update component missing from admin menu.
I also had the same error message after upgrading 3.6.0 -> 3.6.1:
0 Failed to start the session: already started by PHP ($_SESSION is set).
To resolve, you need to use PHP Selector and change from 5.3 (it's a PHP 5.3 issue; will be fixed in Joomla 3.6.2). I change from 5.3 --> 5.6 and am now able to login the administration.
I haven't try it myself. It's a recent discovery of mine in JED, it is called StageIt and it looks promising. StageIt claims it is the ideal staging environment solution for Joomla, making the headache of site updates and development workflow go away.
This taken from the extension's description in JED.
I could suggest the following:
A subscription based service, to monitor, audit, backup, manage, update Joomla sites remotely from a single location. You install the Watchful.li client into your sites and start using the service.
You can setup your sites under a Multi-Sites environment, if your scenario is fitting in.
2 of ...
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 ...
Each extension provider runs their own "update server", the location of which is contained within the extension manifest xml file.
For further information
As far as I know, Joomla itself does not send out update notifications by email. My guess is that you have a third-party extension for this. Akeeba Backup used to send out update notifications, but I think they stopped due to the amount of support tickets caused by this function. It should still be available, but you might have to enable it manually.
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.
For advanced website staging, you could look into Akeeba UNiTE:
UNiTE is an automated, unattended backup archive restoration tool. It
is software written in PHP, designed to restore and customise Joomla!
and WordPress websites from ZIP, JPA and JPS files created primarily
with the Akeeba Backup or Akeeba Solo software suite. It's main
mission is ...
If people can't log into the back-end, there is an additional fix on github here:
You must change the following lines on
private $started; to private $started=false; and
private $closed; to private $closed=false;
Add the line $this->closed = true; after ...
Have a look at the Weblinks repo
It does exactly what you want to do.
The updateserver points to the manifest hosted on that repo.
Download packages are served from the repo as well.
Of course you need to manually update the manifest file with each release.
You can manually download the update package from the following link
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 site (including the database) before you do anything just to be on the safe side.
Hope this helps
I didn't find a solution for this error, what i did was going to Joomla.org download page and download an 3.4.x to 3.4.8 package and installed in the Extensions manager and uploaded it this way. it works now.
It appears that I have clicked that update button little to fast... again...
If I have read official Release News The Joomla! 3.6.1 Update
a little bit more carefully, I would have learned following from the third paragraph:
Updating from Joomla! 3.6.0
Update the Joomla! Update Component through the Extension Manager. Then use the Joomla! Update ...
In addition to the answer by @FFrewin, another solution for updating extensions on a large number of Joomla websites is mysites.guru (formerly myjoomla.com).
You can update all copies of a particular extension on all the websites you have set up in myjoomla.com:
You can also enable automatic updates for a select but ...
I don't see any reason why it shouldn't work. Akeeba Release System (built for software distribution, mainly Joomla) uses URLs like this, and it works for me:
<downloadurl type="full" format="zip">
I read somewhere that Joomla requires a ...
After checking for :
Permissions and all seems to be okay.
Php config settings (memory_limit, max_execution_time etc) all are set at adequate values, so they shouldn't be a problem.
This seemed to be a problem caused by the hosting provider's malware scanner. The restore.php script ('administrator/components/com_joomlaupdate/restore.php') is missing and ...
Are you by any chance running those sites on localhost? I'm asking because I had the same problem with a couple of development sites on localhost.
Either way, you can download the latest patch directly from joomla.org. The 3.3.4 to 3.3.5 patch is only 91.97 KB. Upload and unzip the file to your Joomla root directory, overwriting any existing file.
I went through the changelog on Github and cannot find any references to bug fixes for the extension manager, therefore I don't think it's a big with the extension manager itself.
I believe at the time, it was due to an issue with their update XML file. Either an incorrect download URL or target platform.
What I'd suggest doing is downloading version 2.4.8(...
It is very odd indeed. I think the problem comes from the creator. Then, there is nothing else we can do from downstream.
To solve it, just manually download and update it from T3 for Joomla!. At the end of the downloads list, you can find T3 Framework plugin.