Message "Oopsie"/ malfunction

Hi there,

Can you let us know what version of WordPress you are using and what version of php you are using if you know?

Thanks!

Hi,
I’m using WP 3.9. In the meantime, I tried it on another site of mine and found it working so I suspect it interferes with this site’s theme “Ubergrid” (https://themeforest.net/item/ubergrid-responsive-grid-wordpress-theme/6383212). As the admin interface seems to be Javascript driven, there might be some overlapping JS functions in theme and plugin. I also tried to create the tree on the other site and copy it over into the database, but the overlapping JS seems to be in the frontend too so it’s not showing the tree.
Regards, MM

mmatting – yeah, it definitely sounds like a JS error on your site outside of our plugin. One way we’ve had good luck fixing this is to either briefly try another theme, like the default Twenty Fourteen. Another is to try disabling plugins.

Finally, if you’re comfortable posting the URL of your blog, we’d be happy to take a quick look see there.

Hi,

I have a test tree here: https://www.selfpublisherbibel.de/decision_tree/treetest/
As I’m using the same plugins on most of my sites, I’m almost sure there is a conflict with the Ubergrid theme. I assume it could be solved by renaming some JS functions in the DT plugin… The problem is both in backend and frontend so briefly switching to another team might be useful for diagnosis but doesn’t help with functionality…

Thanks, MM

MM,

I took a your selfpublisherbibel.de link, thanks for posting it. The problem is confirmed to be a JavaScript error caused outside of our plugin. This can be a rabbit hole, so we can’t really take this much further. However, it might be your facebook integration per the errors I saw.

Invalid App Id: Must be a number or numeric string representing the application id. all.js:54
FB.getLoginStatus() called before calling FB.init(). all.js:54
FB.getLoginStatus() called before calling FB.init(). all.js:54

I’m going to mark this issue as resolved, even though I fully recognize your issue may still persist. Best of luck!