Dit onderwerp bevat 2 reacties, heeft 2 stemmen, en is het laatst gewijzigd door Keymaster 3 weken, 4 dagen geleden.
- 23 december 2016 om 10:20 #1931
We believe that after a long time of experience WordPress is poor man’s responsive web design. There are simply too many problems to deal with. Problems which distract us from our real work: to inform our (mainly Dutch) readers about what is happening in the field of classical music, opera and ballet. Instead of spending hours on end to redress what should be okay in the first place. We are not echoing all those positive reports about WordPress and its huge variety of plugins. Usually, the bad news starts with all that updating and with conflicting plugins.
Wordpress needs a separate (SQL) database and a vast number of WordPress files to operate, main portion of which resides in the ‘cloud’ (or in other words on the server). However, we would prefer to have full control on our own hard disk. This simple fact makes it absolutely essential to backup the entire site as frequently as needed, or as felt essential. You should never rely in the first place on the provider being able (or not!) to restore what was damaged, jeopardized or even lost. You need to take this all in your own hands.
What we also have learned is that any plugin, any plugin update, can cause very serious problems or even instantly compromise our website. Just a few days ago it was Supsystic with its database tables which ‘delivered’ update 1.5.0. After installing the update our website was in complete disarray: 50% of our home page kept spinning. After removing the entire plugin through FTP and reinstalling the previous version (which worked correctly), the problem persisted nevertheless. After completely removing the WordPress files and restoring a previous SQL database the problem persisted…the database kept spinning… This drives people mad.
Apart from some blogging or a badic layout we cannot possubly recommend the use of WordPress in conjunction with its plugins. The software, and mainly the plugins (which are ‘authorized’ by WordPress!) is frequently subject to failure after updating, whereas hackers love to use WordPress as their ‘gate of entrance’ to position malware and other unwanted stuff on the website. We had uncountable attacks in the meantime, although with Wordfence as our excellent gatekeeper.
Our latest experiences with WordPress and Supsystic data tables were horrible. Remains the question what Supsystic could do? Well, that is not a pretty story either. We reported the problem and they – of course – responded that their newest version operated excellently. They asked us for user name and password to get into our administrative area ‘to fix the problem’. Who would like that? Well, we finally did, but after TWELVE hours nothing had happened. So we closed the gate. We got back to them later but we did not get any sensible reply by return. A highly disappointing experience.
Our site consists of approximately 5,000 text files. We have not taken these into WordPress but keep them separately. We believe this is the best way to prevent sudden havoc.
At any rate, BE AWARE, despite the millions of people who are using Wordpres to their greatest satisfaction. We do not symphatize with those many hosannah stories out there because our practice shows differently. That is the best hint we can give to you.
- 28 december 2016 om 09:29 #1986
I am using the same plugin and it works quite well for us.
I think it needs to be considered that it is a WordPress plugin. So there simply could be a conflict with other WordPress plugins. In fact, we have faced with similar situation recently. To find the reason of the issue – we tried to deactivate all plugins on our site one by one. It was helpful, we have found the plugin which caused the conflict.
But situations could be different, I just wanted to share my experience of using this plugin.
- 28 december 2016 om 10:37 #1987
Let’s just look at the facts. A website should be consecutively operative. There is nothing more frustrating for any visitor than to find the site either in disarray or not working at all. A failure proof website should be the main goal of any webmaster. One of the basic problems of WordPress are the plugins. These often produce conflicts which cannot easily be resolved. Yes, you can ‘disarm’ plugins one by one, but that does not solve the conflict. The best thing you can expect is that the makers will correct the problem (as long as they see it as problem). I think we are all regularly faced with conflicts caused by an update. That means that neither WordPress nor the plugin makers are really involved in troubleshooting prior to publication. They are not in the position to check each and every plugin beyond their own hemisphere to see if their own update will work or not in conjunction with one or more other plugins. So it is left to the user to perform try and error. That is WordPress’s everyday’s reality. This is why I wrote that WordPress is poor man’s responsive website design. And WordPress knows this perfectly well: they ALWAYS advise to make a full backup in order to be able to restore AFTER an update. Well, that also depends on a program like W 3 Total Cache. This is also something of a try and error. When the cache is completed, operatin in full, it is often hard to get back to the original status prior to installing a specific update. This is OUR experience. Even after cleaning the entire site by removing SQL and ALL WordPress files (no one left really), we have been more than once faced with EXACTLY the same website layout AFTER the update, instead of PRIOR to the update. Don’t ask me why, but it has happened. After having completely cleared the cache it was possible to restore, although it took our site off line for more than two hours (deleting and restoring process). We always do it manually, after so many disappointing experiences with a variety of WordPress backup programms (this is what a lot of people don’t realise: they feel secure after a backup, without ever trying to restore…).
All in all, WordPress is not failure proof. Any performed update is definite. You can’t go back to the previous installation. I’m very sorry to say that there are too many drawbacks and that over the years (WordPress is on the market for many years already) it still has not been able to resolve the main problems involved in updates, no matter where they come from.