Luis Zarza

I fixed the issue. I think it had to do with an overly saturated server.

Once I migrated to a bigger server with bigger RAM and more CPU’s the issue disappeared.

Gotcha, all good now!

Ok, where in your plugin do I set that filter?

Please send a screenshot or a link to your documentation if possible.
Thanks

Hi @tokyobiyori,

Thanks for your answer. Permalinks were set at Post name. I save them again to make sure they are reset, and went ahead to update a post and the same error came up.

As I said before, this error only comes up when All in One SEO plugin is active.
Also need to mention that even if we get the red alert saying “Updating failed”, the update actually happens and it gets saved on the database. I say this in case it helps you troubleshoot the issue.

Let me know next step.

Thanks

Thank you for the alternative solution Marco.

I’ll have your comments in mind.

However have a look at this screenshot from WP-Rocket database tool: https://tinyurl.com/y49yktz7

Yes, that’s right. I use Permatters and WP-Rocket on a daily basis and they both clean a lot of stuff.

Wouldn’t be better to make the option permanent? Your plugin is the only one that shows on my panel every time. The rest of plugins also show a banner when I install them, but then they respect my decision to click on “Don’t show again” and they don’t show back.

Thank you for your comprehension.

It also happens to other plugins similar to Display Posts.

@manuelrocha88 Thank you for your answer. Below’s the info you’re asking for. Also they are not allowing me to post any info for you to access my password protected front-end. Maybe we can communicate via email or another platform so that I send you the password that way?

WP url:  https://wordpress-271710-1281044.cloudwaysapps.com
WP version:  5.4.1
PHP version:  7.4.4
Active Plugins:
 - WooCommerce, version: 4.1.0
 - WP External Links, version: 2.46

WPEL Settings:
array(
'wpel-external-link-settings' => array (
  'apply_settings' => '1',
  'target' => '_blank',
  'target_overwrite' => '',
  'rel_follow' => 'nofollow',
  'rel_follow_overwrite' => '',
  'rel_noopener' => '1',
  'rel_noreferrer' => '1',
  'rel_external' => '1',
  'rel_sponsored' => '',
  'rel_ugc' => '',
  'title' => '{title}',
  'class' => '',
  'icon_type' => '',
  'icon_image' => '1',
  'icon_dashicon' => 'dashicons-menu',
  'icon_fontawesome' => 'fa-address-book',
  'icon_position' => 'right',
  'no_icon_for_img' => '1',
),
'wpel-internal-link-settings' => array (
  'apply_settings' => '',
  'target' => '',
  'target_overwrite' => '',
  'rel_follow' => '',
  'rel_follow_overwrite' => '',
  'rel_noopener' => '1',
  'rel_noreferrer' => '1',
  'title' => '{title}',
  'class' => '',
  'icon_type' => '',
  'icon_image' => '1',
  'icon_dashicon' => '',
  'icon_fontawesome' => '',
  'icon_position' => 'right',
  'no_icon_for_img' => '1',
),
'wpel-excluded-link-settings' => array (
  'apply_settings' => '',
  'target' => '',
  'target_overwrite' => '',
  'rel_follow' => '',
  'rel_follow_overwrite' => '',
  'rel_noopener' => '1',
  'rel_noreferrer' => '1',
  'title' => '{title}',
  'class' => '',
  'icon_type' => '',
  'icon_image' => '1',
  'icon_dashicon' => '',
  'icon_fontawesome' => '',
  'icon_position' => 'right',
  'no_icon_for_img' => '1',
),
'wpel-exceptions-settings' => array (
  'apply_all' => '1',
  'apply_post_content' => '1',
  'apply_comments' => '1',
  'apply_widgets' => '1',
  'skip_post_ids' => '',
  'ignore_classes' => '',
  'subdomains_as_internal_links' => '',
  'include_urls' => '',
  'exclude_urls' => '',
  'excludes_as_internal_links' => '',
  'ignore_script_tags' => '1',
  'ignore_mailto_links' => '1',
),
'wpel-admin-settings' => array (
  'own_admin_menu' => '1',
),
);

• This reply was modified 4 years, 6 months ago by Luis Zarza.

@sterndata I don’t know why it is so hard for you to understand that those are NOT login credentials. Please re read all my messages above. Not just focus on the “”credentials””.

You will NOT be able to enter the WordPress admin with what I provided. My site is a password protected site. Meaning that in order to see the front-end you need to enter a password. That’s done so that Google won’t crawl my website, since that’s a duplicated website.
The information I provided is just to see the front-end the public information.

So again, why cannot I show the front-end of my site @sterndata ?

• This reply was modified 4 years, 6 months ago by Luis Zarza.
• This reply was modified 4 years, 6 months ago by Luis Zarza.

Hi Manuel,

I just updated and the issue it is still there. Can you please check?
https://wordpress-271710-1281044.cloudwaysapps.com/shop/

To see the front-end you will need to enter some credentials.
[redacted]

• This reply was modified 4 years, 6 months ago by Steven Stern (sterndata).
• This reply was modified 4 years, 6 months ago by Steven Stern (sterndata).

Hi Steve,

What I sent are not login credentials.

The URL that I sent is a staging environment of a live site (the live site is not even mentioned on my message above). Obviously I don’t want Google to crawl and track my staging site, so that’s why I placed a password protection for the front-end.

So what I sent are the credentials to simply be able to see the Front-end, those are not credentials to the WordPress admin.

Please check it out yourself. Try and access just the front-end of this WordPress site:
https://wordpress-271710-1281044.cloudwaysapps.com/shop/

You will see that you need to enter some credentials.
[redacted]

• This reply was modified 4 years, 6 months ago by Luis Zarza.
• This reply was modified 4 years, 6 months ago by Steven Stern (sterndata).

Hi @ketorecepten , yes you can remove GADWP plugin. I’ve replaced GADWP with GAinWP successfully on all my sites.

Ok, so should I remove the plugin until is back up?

Ok, so I did what you suggested and I solved the problem.

Thanks for support.

• This reply was modified 5 years, 11 months ago by Luis Zarza.

Ok, I just cloned my the website on different server and the widgets are available again. Do you have an idea why this could be?

I mean what could be the setting to change on the original server to make it work.

This are the server environments in both cases.

New one:
Server Environment
Operating System: Linux
Software: Apache/2.4.10 (Debian)
MySQL version: MySQL Community Server (GPL) v5.7.24
PHP Version: 7.2.12-1+0~20181112102353.11+jessie~1.gbp55f215
PHP Max Input Vars: 2500
PHP Max Post Size: 64M
GD Installed: Yes
ZIP Installed: Yes
Write Permissions: All right
Elementor Library: Connected

Original one:

Operating System: Linux
Software: Apache
MySQL version: MySQL Community Server (GPL) v5.6.41
PHP Version: 7.2.13
PHP Max Input Vars: 1000
PHP Max Post Size: 8M
GD Installed: Yes
ZIP Installed: Yes
Write Permissions: All right
Elementor Library: Connected

• This reply was modified 5 years, 11 months ago by Luis Zarza.