ventsmagazine

Thanks! What I meant is that I see there’s an addon for frontend posting. I am guessing that has the option to make it also a paid submission form for guest posts and what not? My question is, if thats the case, do people need to be signed on to use that form or they can access and post without having to sign up?

Ok, so I deleted the mu-plugin thing and what it did was to delete the must use section on plugin. It did disappear… its weird, because its been a long since I’ve used any null…

I am doing a virus check anyways…

Also I cleaned both site and browser cache.

Thanks!

Will check on the rms thing.

However, I just made a new discovery. Apparently on my Chrome browser where I have been writing all this time, and mostly use, the site never wanted to load. HOWEVER, on every other browser on my laptop, the site loads ASAP. Then I clean my cache, and now everything kinda lows better on Chrome…. weirdly enough, for other people using Chrome, they seen to either load fast or not.

So maybe that’s what the cache message I sent yesterday meant? My site isn’t cleaning very well the cache?

I did some research and if you go to plugin there’s a Must use section and apparently is that.

Also query monitor found this as a PHP
The APCu extension for PHP is installed but is not in use by WordPress
The Memcached extension for PHP is installed but is not in use by WordPress

Have you heard about this?

Again, posting seems to go smooth. But now site is loading VEEEERY SLOW on Desktop but on mobile it loads a bit much faster.

Also, do you know if the current WordPress version supports PHP 7.4 and MYSQL 5.7?

I already deactivate Yoast. Seems to be working fine, at least in the posting its quiet fast now…

I did install query monitor (apparently many people here use it) and I see in PHP errors have this two:

Undefined index: token 1 +
wp-content/mu-plugins/rms_unique_wp_mu_pl_fl_nm.php:6
MU Plugin: rms_unique_wp_mu_pl_fl_nm.php

When I click on the + icon to learn more on that error I get this:
remote_sign_in()
wp-includes/class-wp-hook.php:287
do_action(‘init’)
wp-settings.php:540

In Slow Queries I get this:
SELECT COUNT( 1 )
FROM wp_posts
WHERE post_type = ‘post’
AND post_status NOT IN ( ‘trash’,’auto-draft’,’inherit’,’request-pending’,’request-confirmed’,’request-failed’,’request-completed’ )
AND post_author = 1 +
WP_Posts_List_Table->__construct()
Core 1 0.3559

SELECT post_status, COUNT( * ) AS num_posts
FROM wp_posts
WHERE post_type = ‘post’
GROUP BY post_status +
wp_count_posts()
Core 4 0.0919
SELECT SQL_CALC_FOUND_ROWS wp_posts.ID
FROM wp_posts
LEFT JOIN wp_postmeta
ON (wp_posts.ID = wp_postmeta.post_id
AND wp_postmeta.meta_key = ‘rms_rm_uniq_meta_post_id’ )
LEFT JOIN wp_postmeta AS mt1
ON (wp_posts.ID = mt1.post_id
AND mt1.meta_key = ‘rms_remote_featured_image’ )
WHERE 1=1
AND ( wp_postmeta.post_id IS NULL
AND mt1.post_id IS NULL )
AND wp_posts.post_type = ‘post’
AND (wp_posts.post_status = ‘publish’
OR wp_posts.post_status = ‘future’
OR wp_posts.post_status = ‘draft’
OR wp_posts.post_status = ‘pending’
OR wp_posts.post_status = ‘private’)
GROUP BY wp_posts.ID
ORDER BY wp_posts.post_date DESC
LIMIT 0, 20 +
WP_Query->get_posts()
Main Query

Core 20 4.0838
SELECT DISTINCT YEAR( post_date ) AS year, MONTH( post_date ) AS month
FROM wp_posts
WHERE post_type = ‘post’
AND post_status != ‘auto-draft’
AND post_status != ‘trash’
ORDER BY post_date DESC +
WP_List_Table->months_dropdown()
Core 54 0.2467
SELECT wp_users.ID,wp_users.user_login,wp_users.display_name
FROM wp_users
INNER JOIN wp_usermeta
ON ( wp_users.ID = wp_usermeta.user_id )
WHERE 1=1
AND ( ( wp_usermeta.meta_key = ‘wp_user_level’
AND wp_usermeta.meta_value != ‘0’ ) )
ORDER BY display_name ASC +
WP_User_Query->query()
Core 71 0.3554
SELECT wp_users.ID,wp_users.user_login,wp_users.display_name
FROM wp_users
INNER JOIN wp_usermeta
ON ( wp_users.ID = wp_usermeta.user_id )
WHERE 1=1
AND ( ( wp_usermeta.meta_key = ‘wp_user_level’
AND wp_usermeta.meta_value != ‘0’ ) )
ORDER BY display_name ASC +
WP_User_Query->query()
Core 71 0.3681

So you think it has to do with the posting then?

So all it was running pretty smooth after I did this, even the CPU went down like I mentioned.

Then this morning I signed into the site, went in and posted an article, all good… then the second, when uploading the picture it said it couldn’t upload because the server was down. I tried to refresh and all and I was just getting 502 and 504 errors. Then I deactivate all plugins and did the same, all working fine now, except for a few weird things now:

When the server was down, I got a “disconnected” error, something even when I had the issue the past two days never happened. In fact it hasn’t happened to me in years. I tried browsing other pages and my internet seems to be working fine.

The picture it never got uploaded. When all got fixed, it did get uploaded.

Also when the server and all was supposedly down, another author posted two posts. So how did she get to post and I was getting error?

Also on my server when trying to see how it was peaking, it kept loading the new information of the CPU, without giving me the info. However I navigated through other tabs and the hosting site was working fine. Also, also… checking in detail the CPU it shows it has never peaked like to 100%. In fact in moments were it was high, it show the CPU was kinda low at the moment :/

Last but not least, when setting up Jetpack again, it says it can’t for connection problems, SSL issues or something else. :/

I’m starting to feel more confused than Tim Robbins on Jacob’s Ladder

It actually seems to kinda be working now on Desktop… very weird. I did, however, didn’t activate VaultPress and the Yoast Google News plugin. Maybe one of those?

It actually kinda did. When I try to visit the website itself on Desktop its running rough for me, but on my mobile and I am posting things quick enough. So it technically did work re-activating.

Hi James!

I did that… it kinda seems to be back to normal. Did you or anyone here faced any peak or something when updating YOAST or Jetpack? I did two updates of those two before everything happened.