Both Wordpress and Joomla! are highly-regarded and each have there unique advantages when you compare them.
To answer your questions:
in the software architecture between Joomla! and Wordpress
Joomla is OOP (object-oriented) and MVC (an object-oriented design pattern).
Wordpress is written in Procedural code.
Procedural programming specifies the steps ...
When Joomla core is updated, no overrides in your template folder should be affected. That's why they exist.
On core Joomla items, overrides are going to only rarely conflict with Joomla core updates. When you override the Joomla core files, or any files, document document document. Commenting in the override file is CRITICAL if this is going to happen ...
Upgrading a template should be as simple as using the Joomla installer to upload and install the updated version of the template.
For it to work, though, the templateDetails.xml file must define the 'method' as 'upgrade', rather than 'install'.
You can check this by unzipping the template install file, opening the templateDetails.xml file and check for the ...
I can't imagine a better tool than git. This is a great tool for tracking the changes that you make to code (if you are making any), is the system used by Joomla for contributing code (which is an awesome thing to do), and this is its purpose!
The workflow is pretty simple and should allow you to be pretty worry free:
Back up your joomla website (which you ...
Sounds like a permissions issue.
In the Joomla backend, go to:
System (top menu) >> System Information >> Directory Permissions
Make sure all files and folders apart from the global configuration.php are writable.
If they aren't, then you will need to change the permissions, so that all folders are set to 755 and files are set to 644.
You can either do ...
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 ...
This is not coming from Joomla core, but from a 3rd party (likely custom developed) component that exist in your site.
First see if you really need/use this component, or you can simply uninstall it. If you need it, then look for any information you can gather for this component - find the developer and his site/email and ask if there is an update for ...
You can't prevent Joomla from upgrading her core templates. They are in there for a reason as a part of default installation. I am afraid you will just have to learn how to live with them. I did the same, because they used to bug me before, but not anymore...
But if you really want to move them out of your way, you can always Disable them in
Extensions | ...
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 ...
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. ...
Suggested readings are "Adapting a Joomla 1.5 extension to Joomla 2.5" and the "Creating A Search Plugin" article on Joomla Docs.
Actually, that code look's like a Joomla! 1.5 era search plugin. However, it's not of a standard form… the second method you have plgSearchHotels() follows the naming convention for Joomla 1.5 but the variables passed to it don't ...
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 ...
As others pointed out, Joomla does not install PHP. Upgrading or installing Joomla will not change your PHP version. PHP is usually installed and updated by your hosting company (or by yourself if you manager your own server).
Joomla 3.3.6 requires PHP 5.3.10 or above (5.4 + recommended). According to your screenshot you're using PHP 5.4.32, so you should ...
The were session storage changes in the Joomla 3.4.7 update.
To fix the issue, you simply need to logout and log back in before you can make any article changes.
I think to truly answer this question, you need to be extensively familiar with both WP and Joomla!. I'm Joomla! heavy and have only used WP a few times, so my answer may not be as full as you might hope.
WP is first and foremost, a blogging platform. It's set up for feeds of data. You have to go out of your way to move past the feed default to get a ...
Template overrides are the only way to do this. In terms of the form fields we're working on creating JLayouts for these form fields so you can override them (see https://github.com/joomla/joomla-cms/pull/3231).
However currently as @Anibal says this isn't possible in J3.2.
Joomla is not shipped with PHP, therefore if you update Joomla, it will not update your PHP version.
PHP is a server side language and must be upgraded my either yourself or your host. Only some hosts (if you're on a shared hosting package) allow you to select a different PHP version. The reason being is that on some shared hosting packages, the same PHP ...
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....
It's an "opt-out" feature to encourage more people to keep their sites up to date. Loads of people either forget or don't think it's important so telling them straight away rather than letting them find out in their own time is the best option.
The only thing you can do is either:
Disable the system plugin on the sites
Block the emails ...
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 ...
This is an extension of FFrewin's answer. Akeeba also produce a free tool called SiteDiff. It allows you to compare 2 sites that have been backed up with Akeebabackup (there is a free version of that too).
To get this to work, you would have to have 2 backups. One backup would be of your site (let's say it was version 2.5.19).
For the other backup, you ...
I just did a quick test, and it looks like you can unzip the Joomla 3.4 Full package to your testing environment, overwriting any existing files. After removing the installation folder (not required for testing releases, but final releases requires you to remove this folder), everything seems to be working, and Joomla admin area reports Joomla! 3.4.0.
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.
What I do is to go in:
Extensions -> Manage
and disable any extensions, templates that I don't use. Of course if we are talking about 3rd party extensions, I totally uninstall them - but disable for core extensions does also work, so they are out of my way in most administration tasks.
In Joomla 2.5.18, a new Password Security, based on PHPass, was introduced.
When a returning user visits your site, the password is encrypted with the new method.
There's no database structure change. http://developer.joomla.org/version-2-5-18-release-notes.html
Write a small script which calculates md5 of original-files which you have done over-riding.
Dump these file-path and MD5 into a file in your template
Whenever joomla is updated, run the above script again.
Check the difference in MD5, if any then you need to check it out.
Tip: Override the files only if those changes cannot be done by CSS overriding.
I'd suggest turning on the built in developer tools in your browser and monitoring the network requests being made. Each "step" in the update process is being done via AJAX and it's possible there's an error message not being displayed on the page but it can be found by reviewing the contents of each request.