TheWatcher2

The latest version of SiteOrigin Widgets Bundle (v 1.11.2) appears to have solved the problems with Beaver Builder. Everything in Beaver Builder seems to be working normally. Thanks for the very quick help!

The latest version of SiteOrigin Widgets Bundle (v 1.11.2) appears to have solved the problems. Everything in Beaver Builder seems to be working normally. Thanks for the very quick help!

I’ve also noticed the same issue with the latest version of SO Widgets Bundle (1.11.1), and I’ve posted the problem on the Beaver Builder support page. It also may have been a problem with the previous version of the Widgets Bundle, but at that time I didn’t correlate the two plugins as incompatible. When I deactivate the Widgets Bundle, the problem with Beaver Builder goes away. However, when it’s active, no edits are possible with Beaver Builder.

Hope you can solve the conflicts.

Thanks!

Thanks for your help Alexgso!

The other plugins I’m currently running include Admin Custom Font, Beaver Builder Lite, Bible Verse of the Day, Black Studio TinyMCE Widget, Contact Form 7, Disable REST API, Feedzy RSS Feeds Lite, Genesis Dambuster, Genesis Simple Edits, Google Analytics for WordPress, Google Analytics Dashboard, Google XML Sitemaps, HTTP/HTTPS Remover, MetaSlider, Page Builder by SiteOrigin, RefTagger, Shareaholic, UpdraftPlus, Widget Importer & Exporter, Wordfence Security, WP Edit Pro, WPSSO, and Yoast SEO. I normally also have the SiteOrigin Widgets Bundle active, but I’ve deactivated it to be able to run Beaver Builder. It’s only when SO Widgets Bundle is active that I see the problem with Beaver Builder. Also, I’m running Genesis with Dynamik Website Builder as my theme.

I’ll also post this on the SO Widget Bundle plugin site. You guys should probably contact them.

Thanks again!

I have determined that SnapID is incompatible with the plugin Wordfence Security. Wordfence has a number of login security options to prevent hacking attacks. After disabling Wordfence on my test site, SnapID worked fine with 2-factor authentication enabled. It did not bring up the “Cheatin Huh?” message either, but worked perfectly. Note that a previous 2-factor authentication plugin I used (Clef, which is no longer available) worked well with Wordfence enabled. SnapID must use a protocol that conflicts with the Wordfence Security login options. I hope you can overcome these conflicts, because I believe SnapID could be one of the best authentication options available for WordPress sites.
Thanks!
Greg

When I get a chance, I’ll also try disabling all my plugins on my test site and then installing SnapID. Then I’ll re-enable each plugin and check the results. I’ll get back to you if I can identify the culprit.
Thanks,
Greg

Thanks for your quick response. Unfortunately, the plugin started to completely lock me out of my site with the same “Cheatin’ Huh?” message. After deleting the plugin, the login with my user name and password worked fine. I next did a Wordfence Security scan for malicious code, and it found nothing unusual. I also took a quick look at the files on my server and found nothing out of the ordinary. The error log also didn’t flag any suspicious activity. I can be sure my site isn’t infected, because Google typically finds this quickly with their crawlers and would send me an immediate message indicating a compromised site and shut down my Adwords campaign until it was fixed. It appears that the problem is originating with the SnapID plugin. I downloaded it directly from www.remarpro.com. Hope you can get this figured out.
Thanks,
Greg

After working on this issue for a couple hours, I finally uninstalled Clef and reinstalled it on each of my sites. This appears to have fixed the problem; however, I don’t know if updating the plugin or updating my phone app was the cause of the problem to begin with.

Yoast SEO is becoming painful. I rolled back to the previous version, but the 404 error remains. The latest update really screwed up my site.

Sitemap in latest update also does not work for me. When I click on “You can find your XML Sitemap here:”, it returns a 404 error. All the solutions in this discussion did not work. I’ll definitely roll back to the previous version until they get the bugs fixed.

Mika,

Thanks for the response. It appears that WP has linked its success to a program (TinyMCE) that now has dramatically reduced functionality. I realize that the authors of the program say it has been enhanced, but to we who just want to get work done, it is a significant step in the wrong direction. Even on the TinyMCE web site in their FAQs section, they admit that the image editing options have been removed, and they recommend that you “use the Style Formats option instead, which is much more powerful”. What they mean is that the user is left to code in their own CSS for each image, for which they provide an example of setting margins. This is incredible! It is like the next version of Microsoft Word having coding options for simple text formatting, such as bold or italics. Users don’t want to code or learn programing; they just need to get work done. I run two sites with lots of graphics and each image has CSS tweaks to get the formats just right. If I have to code each image to do what I used to be able to do just by filling in a dialog box, WP has failed me in the most basic way possible.

TinyMCE has made a huge error in not taking into consideration its customers before removing ease-of-use options. The overwhelming majority of their customers are not advanced web site coders; they are people putting content on the web as efficiently as possible using WordPress. We users want better ways of doing web page design, not more difficult ways. WP developers need to carefully listen and solve this issue quickly, even if the problem comes from a program WP doesn’t control but has unfortunately hitched their wagon to.

I have now successfully migrated back to WP 3.8.3 and everything is working again! Thank God for backups! I wouldn’t recommend upgrading WP to v3.9 until these issues are TRULY resolved.

I’m not a developer, but I have the same need of rapidly adjusting the margins, padding, and borders of images on pages and posts. I never anticipated that the so-called “new and improved” image editing capabilities of WP3.9 would actually be a significant downgrade from 3.8! I’m putting together a single page right now with over a dozen images that need css tweaking. Now that I have to do it by hand it is taking forever! Who decided to cripple the image editing features in WP? My experience with v3.9 is so bad that I recommend no one upgrade until this issue is resolved.

In my opinion, WordPress 3.9 for image editing within posts and pages is a disaster! I used to be able to add borders around images, padding, margins, etc., just by entering data into the image editing dialog box. Now what should I do–code each image by hand? This is a step way back feature-wise. It has impacted every page and post I work on.

I have a suggestion, how about WP 4.0 going back to coding only with no visual design? Maybe we can go back to DOS while we’re at it, too!

How can I revert back to WP 3.8 so I can get some work done? I will turn off auto-updates from now on.

WordPress 3.9 for image editing within posts and pages is a disaster! I used to be able to add borders around images, padding, margins, etc., just by entering data into the image editing dialog box. Now what do I do??? Code each image by hand? This is a step way back into the past. I know, how about WP 4.0 going back to coding only with no visual design? Maybe we can go back to DOS while we’re at it, too!

How can I revert back to WP 3.8 so I can get some work done? I will turn off auto-updates from now on.