Support Forum
I took a look in the SP Error Log: No Entries (just some "Notices" but unrelated to the time I activated)
The peaks in the load are not, when I activate the plugin, but when I call the Main Page. I confirmed this now with the minute view on Load.
And gravatars are not used and the caching is turned on. Again, the installation is still on near zero posts.
So what happens seems to be obvious now:
When the main page of the blog loads, it tries to load the "recent Mingle Posts" AND the "recent Simple:Press Posts". And that seems to cause the loop. Deactivating the widget of either one, makes the trick. Either of them causes below 1 second for display. So both work like a charm when used alone. But both together, somehow "block" each other and "loop" for almost 30 seconds on heavy load.
Obviously there must be some interdependency, where both plugins use some "bottleneck" in wordpress, that causes this behaviour.
It is beyond my reach to guess about the cause. Only you know, what function this widget is using.
well, we know what our widget is using, but not the mingle one... and of course there is no loop per se... and like you not sure what between the two would cause them struggle with each other...
do you have any access to mysql profiling tools? would be curious to see if its a query or other... even the wp debug facility with some of the add on plugins for monitoring performance might provide some insight...
what storage engine are you using in mysql? myisam or innodb? the latter is better from performance standpoint and locking mechanism within mysql... if the former, perhaps you could try our conversion tool for moving to innodb and see if any different...
Visit Cruise Talk Central and Mr Papa's World
a lot of questions and a lot of work to chase for a cause. I guess you know that and this message might be the intention of your questions.
The answer is simple. As the priority of the problem dropped to "annoyance", there is no justification in spending valuable lifetime in chasing, what cannot be immediately narrowed down by you.
So either you have an immediate idea, what could be a concrete candidate for such an interdependency. If yes, I am willing to do some further, limited testing. Otherwise I dont have the time to search for a needle in a haystack.
So I will rest the case for now. Hopefully, this symptom is not just the tip of a bigger iceberg.
I think I can only echo what Mr Papa said above. The code for the widget really is very straightforward and simple and yes - we don't know the Mingle code at all.
I would have thought the only point of contention would be the WordPress 'users' table but mySQL should be able to cope with that with no problem.
The point Mr Papa made regarding storage engines is a good one however. I do not know your knowledge level with mySQL but MyISAM tables (the usual default) do perform whole table locking when they are accessed whereas innoDB tables perform row level locking. Having said that, of course, one doubts that there should be any writing to the DB during a recent posts listing. And for such small amounts of data one would also assume that it should be available in mySQL's rather efficient cache.
YELLOW
SWORDFISH
|
I fully agree. And I fully understand and accept, that you have no crystal ball either.
For me, it is just not worth the time, to search in the dark for a problem, that is just "annoying".
Life is too short for that and I am of an age, that understands that well 😉
Thanks for your help. The matter is closed from my side - as long as it doesnt pop up somewhere else 😉
understand the age point! 😉
let us know if something else pops up...
Visit Cruise Talk Central and Mr Papa's World
Hi,
in the conversation above I said, I will wait for the Profile Options Bug to be fixed in the next version, instead of changing the code myself.
What I didnt ask, was "when" a new version is due, as I was obviously under the - maybe faulty - impression, that a new version will be due before christmas.
So I tried to change the code myself as outlined in post (3) in the following thread:
https://simple-press.com/suppo.....r/#p156009
Unfortunately it doesnt work. And yes, I have found the line, changed it exactly as outlined and saved/have overwritten the sp-api-common-display.php in the right folder again.
But I still get this on the Profile Option:
Fatal error: Call to undefined function is_plugin_active() in .../wordpress/wp-content/plugins/simple-press/admin/panel-profiles/forms/spa-profiles-options-form.php on line 71
Two Questions:
(1) What did I miss? Why doesnt it work?
(2) Is there a new version in planning and if yes, roughly when? I dont expect a concrete date, just a general indication of a timeframe.
I am asking, because I want to make a plan, when I will go Live with Simple Press as new Forum. Without the Profile Bug fixed, I cant.
Thanks!
Hey Hari,
How did you go about copying the code? You need to make sure you use a plain text editor if you're doing this on your desktop as rich text editors convert quotes in code to rich text quotes which will cause problems.
The last I heard 5.6 was planned sometime in early December, but will need confirmation on that one!
Hi Ike,
yes, I know. I simply used the "Windows Editor", a plain txt editor. Not even Wordpad, not Word and no special code editor.
I also checked afterwards, by downloading the sp-api-common-display.php after the change via ftp. The changes were made and look OK as described in your post.
I changed the type of the file to txt for you and added my version to the attachement of this post. So you can take a look for yourself.
Any ideas?
Reading through this again - and to be honest, not having actually been involved in this bug so coming at it for the first time - I am not so sure we are talking about the same thing here.
It says in the bugfix notes that this function IS available in the WP admin yet it seems to be here that you are actually having the issue.
Could you do me a favour? At the top of the file pointed to in the error entry path (admin/panel-profiles/forms/spa-profiles-options-form.php) could you add the file include line:
include_once(ABSPATH.'wp-admin/includes/plugin.php');
Say - immediately after the function name at the top - in between that and the closing php tag/opening script tag...
And - just to confirm - our next update is being primed to coincide with the next WP update due, I believe, 4th December.
YELLOW
SWORDFISH
|
1 Guest(s)