Jon Schroeder

I actually got this working by disabling come components of Jetpack. Here’s what I have enabled:

Comments
Subscriptions
Carousel
Tiled Galleries
Sidebar Widgets
Enhanced Distribution

Perhaps that helps narrow it down?

I’ve noticed this bug as well; for me, this appears to only delay it showing up (by about 15 seconds) — and importantly, the bug only appears on the admin section. If you aren’t logged into the site, it’s showing up normally.

Is that the case for you as well?

I’ve actually downgraded to 1.5.5, but with no success. Any ideas?

This appears to be broken as of the most recent version. This site used to work, but is now broken as a result: https://myego.org.

Any ideas/fixes? I’m hoping to fix that site as well.

Thanks!

I simply downloaded the old version (https://downloads.www.ads-software.com/plugin/testimonials-by-woothemes.1.2.1.zip), deleted the new version of the plugin, and uploaded the old one.

Fixed for now, and I’ll wait for the next version to upgrade.

So that you can diagnose — I was seeing the same thing; I’d thought for a moment that I was seeing a CSS error, but when I looked, there was nothing being output in the HTML.

Best of luck, Matt!

Is there an easy way to simply downgrade the plugin while we’re waiting for a fix? I’m using the Appply theme with Testimonials displaying on the home page (not the shortcode), but I’m having the same issue after upgrade.

Any of you guys know the specific thing that’s causing it (the specific code causing this error)?

I’m running into it as well using a variation of BootstrapWP theme, but I have it working using that theme in another location (can’t figure out what’s different, as the two installs are on the same server).

Anyone have even a partial solution? I’m considering just hand-coding custom post types going forward, which would be OK, but it means that my existing custom post types aren’t particularly editable in the meantime.

Update: the rollback worked for some of my sites, but not all. Version 1.0.4 is working normally, but versions 1.1.3.1 and 1.1.3 are still having the same issue.

Anyone else seeing this?

Could be. I ended up rolling back my entire server over it, but it’s working again now.

I’ve replicated this issue on a clean install of WordPress with just the Types plugin activated. I still believe my server is the issue, but would appreciate any help anyone could provide.

Huh. They were working of getting rid of it? Working on a paid method to get rid of it doesn’t really count.

Lame. Guess I’ll be looking for another plugin –?I like it and would have probably bought it, but not a monthly fee for the privilege simply of not having to advertise for the company I’m paying.

No, the option to redirect doesn’t seem to have an effect; I tried using Peter’s Login Redirect plugin to circumvent that option, but the redirect option doesn’t seem to have any effect at all.

Email me directly at [email protected] and I’ll send you a screenshot, if you like.

users come up with solutions that actually work

Meant just inspecting the element. That’s the solution that works that you don’t want people using.

Also documented months ago. Please read
https://quirm.net/wiki/eshop/troubleshooting/cant-switch-eshop-to-live/ before posting “fixes” on this issue.

You’re absolutely right. No one else help, please! (You’ll note that the only link in my initial post was to your wiki’s guide; I’m not exactly directing people away.)

In any event, thanks for all that you do (sincerely), [moderated] and have a good one!