chunky2010

Thanks. I was just wondering how to work with it. It’s a bit disappointing to know that I can only use shortcodes because to my knowledge that means I can’t experience a visual representation of the page unless I save and refresh on a different page, correct?

Hi Shycoder,

Have you been able to find out anything new about my problem?

Thanks,

C.

Hi Shycoder,

Thanks for your help so far. I’ve decided to give cleaning up the DB a try before contacting Calendly. I’m using Advanced Database Cleaner plugin. Can you tell me what to look for in the DB? I’ve already deleted your plugin and intend to delete any records in the database related to it.

Thank you.

Sorry for the late reply. I was out of town on business last week.

So I’ve tried everything at this point, minus editing the DB directly and removing any added fields from the plugin. Nothing seems to fix this.

I should also let you know that I’m using a WP multisite. Not sure if that has any bearing at all.

To recap:

1. I replaced the API token that was from my account with the client’s API token.
2. I cleared cache on both the main network site and on his child site.
3. I deactivated the plugin from the main network site and reactivated it.
4. Cleared cache yet again.
5. Removed the API string altogether to get it to error out on purpose, hoping something stuck might clear.

No dice.

I’m really scratching my head here because one would think that with all these steps something would work. It just doesn’t make sense.

Thoughts?

Thank you again for your help!

• This reply was modified 2 years, 11 months ago by chunky2010.

Yes, correct. I replaced the API key but no changes

When you say replace the url, what do you mean, specifically?

And if I clear the site cache in the admin panel could that fix it?

Thanks for your help.

Yes, I tried to sync before posting, and just tried again but no change.
Any ideas?

First, thanks for your quick reply. I really appreciate it!

Yes, I can disable Gutenburg (and I don’t like it anyway, the old school editor was working just fine), but the issue will persist. For some reason editing content outside of the page builder breaks the layout and even hides some content. This is why you have to go back to the page builder and republish it. And again, to be clear, I think Yoast is simply a victim in this situation. The real problem is with the text editor and page builder, as you also confirm. But the bottom line is it makes for a huge amount of confusion and cognitive load on the part of a non-technical user. And naturally so because it’s a segmented/broken user experience.

I guess the best we can do is to ask them to use your online tool for the SEO work and then copy/paste into the page builder? What are your thoughts?

Thanks again.

Thank you, I’ll check these out.

Thanks. I have my own dedicated server, so I will check into that.

I adjusted the number of posts to display to “60”, since there are about 53 of them total.

C.

Thanks.

But yes, I did that before posting. I turned off all plugins and changed the theme back to the default theme, but had no luck.

Since posting last time I did remove any non-essential plugins and as a result the admin panel is now working again. However, the Posts list problem persists.

Thanks,

C.

Thank ou hogetan,

I turned on debugging and here is the error message I’m getting:

Notice
: wp_enqueue_script was called
incorrectly
. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see
Debugging in WordPress
for more information. (This message was added in version 3.3.) in
/home/needscen/public_html/wp-includes/functions.php
on line
3049

Notice
: get_theme_data is
deprecated
since version 3.4! Use wp_get_theme() instead. in
/home/needscen/public_html/wp-includes/functions.php
on line
2908

Also to note, the admin panel is now only a white screen of death, aside from the error message I’m getting.

Thoughts?

Thanks again,

C.

No, not multisite, just a regular WP install.

The issue is that the url must change.

Bumping for visibility. Pardon me for doing so.