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 ...
You can definitely delete the files in the tmp directory and actually it is strongly recommended to do so and maintain it clean.
You should only keep the index.html file in place, that may prevent potential directory listing of the files.
The tmp (temporary) folder is used by Joomla and its extensions when performing software installations or during the ...
1. What does this padlock mean:
Joomla Core Components like content (articles), categories, menu, modules, extensions, etc, contain in their database table structure a field called "Checked-Out", which can take 2 values: "0" for Checked-In status, or the actual user ID for Checked-Out status.
When any user is editing a specific item e.g. an article, Joomla'...
Ideally, you should probably be doing Joomla and third party extension updates and some of the other checks more than once a year.
On a regular basis, run a backup and update to the latest Joomla version.
Ideally subscribe to the Joomla Security News feed so you are kept informed of core Joomla security updates and apply any high ...
The "tmp" folder is a place for the system to store files on a temporary basis. One of the most frequent uses of this folder is when extensions are installed. When a new extension is installed, a copy of the extension's archive file is copied into the "tmp" folder and then is unpacked into the correct Joomla folders.
The install process doesn't clean itself ...
In addition to @FFrewin's answer, if you do not have FTP access, you can clean the tmp folder using Admin Tools. The option for this is located on the Admin Tools control panel as shown in the below screenshot:
As mentioned by FFrewin, the Pro version of Admin Tools allows you to perform a scheduled clean up of the tmp directory.
In addition to this, you ...
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 ...
To answer 'what is the technical reason', I took a look through the tracker and GitHub notes. The issue seems to be two-fold - a failure to delete certain files during the upgrade, and failure to apply certain SQL updates. However, if only affects some and not others. See the bug tracker for additional info.
The general best practice option approach seems to ...
There's a few things to consider when planning migrations between major versions. One of the top ones should be the end of support or EOL date for the version you're using now; if that is close, you should be planning your move.
For established websites, I'd suggest looking at the available features. Does the new version have something you need soon? If ...
I'm not sure there is a best method on how to do this. The only way I can think of requires a bit of effort. That is, generating a list of all the images in the content table in the database (and potentially in modules, menus, banners, etc... Any place where images are referenced which is a lot), compare that list against all the images on the files system, ...
I recommend double-checking any rules you have loaded through your .htaccess/web.config file. I've seen people throw in custom rule-sets to manage the /administrator/ directory that don't quite cooperate with their hosts Apache/IIS configuration.
Of course, it maybe worth loading a fresh Joomla instance under a subdomain or another account under your ...
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 ...
If you have your access logs, you might be able to pull out all the requested image files in the last X months (you will need to play with all this data). So these are very probably in use in your actual site (yet not 100%).
Depending on your content and site structure and if your site is not really huge (i.e. 1 million articles), it is very probably that ...
I'm not aware of an existing extension that would do it. Your best bet would be to write a script that checks each image against tables in the database where content can be stored to see if they are in use.
As you are talking about architecture, it does matter when you are building a portal or a complex website i.e. lots of inter-connected entities.
Joomla source code is object oriented.
Joomla code is very well divided i.e. applications, plugins, components.
Most of the design patterns are followed in Joomla, e.g. Factory, Decorator, Dependency Injection, ...
In general, it's always good to uninstall any extensions you're not using. By not doing so, you're cluttering the Module/Plugin Manager, your database and using more space on your server.
So any plugins, modules, templates or components you're not using, uninstall them.
In regards to databases, I'm not really an expert in them, but I can only assume that ...
The #__ucm_content database table is used to store tags for core extensions, so I would not remove them, else you may get an error along the line in the future.
See more information tags with extensions here:
hope this helps
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 ...
The problem only appears on certain servers, for reasons I don't yet know exactly.
On my servers it works without issues, but a friend had this problem as well.
I have done a PR which I believe will solve the issue, see https://github.com/joomla/joomla-cms/pull/3467. If someone who has this problem can test this patch and see if it fixes the issue, then ...
Starting from Joomla! 3.4 every version will be a stable one and will have support at least two years unless the new minor version will be released. If it will happen then the previous minor version will not be supported and the current one will be supported at least two years. So if you are planning to migrate to 3.x series, then you are safe do it from v3....