kot41
Forum Replies Created
-
Logs and will grow until you fill the database and do not damage the table after that you yourself will not go on to your site! also if the server is installed on the server redis then there is a chance not to get to the domain at all! this is due to the fact that the developers broke version 6.8.1 which was a beta version (that the developers released it as a release is a bug) and quickly released version 6.9.0. (completely non-working alpha release and immediately released 6.9.2. as you have I recommend urgently to roll back to version 6.8.1. there is cleaning logs! Yes, the motivation of developers is that if the site was hacked, you can learn from the logs that there was!
I will reply if the site is hacked then immediately completely remove the plug-in from the system!
Version 6.9.0-.6..9.2 are FORBIDED FOR MANY DATES OF THE CENTERS IN GENERAL!On my business hosting on which 76 servers are installed deleted this version of 6.9.0 with more than 300 sites! in addition to the cleaning button there are still a number of problems about which in 90% here it is written in different topics! Filled with the previous version 6.8.1 which does not have these problems! I recommend everyone to simply roll back to the old version and wait for the solution! Also I ask the developers to make changes to the list of changes! So that our test team can test these changes on our test servers before the global update on the working sites!
The new update and the lack of a clear log button caused a number of critical problems in the operation of databases! I did not want to describe them all here! Did a rollback to the previous version of the plug-in by clearing all the garbage (yes it’s rubbish! Logs can not be called logs) forbade updating on more than 200 sites of this plug-in! waiting for a solution to the tune! My personal rekomedatatsiya not buy a premium of this plagiha until normal will not write a list of critical changes!