scherii

If anyone doesn’t want to wait, until it gets fixed officially, you can fix it like this:

In /wp-content/plugins/flamingo/admin/admin.php go to line 9 and change
add_object_page to add_menu_page.

Image for reference

Hi Matt,

Thank you for 1.2.7, it solved the problem.

(And yes, I did test it with no other plugins enabled. As of 1.2.6 Better Search Replace did not show up under ?Tools?).

Have a great day!

I have the same problem as Jemmey and have tested it on multiple sites (4.3.1).

It’s not in the menu “Tools” and (I suppose the URL is correct) also not if I try to access /wp-admin/tools.php?page=better-search-replace.

Please let me know if I can help you debug it.

I second that ??

Just wanted to bump this thread as it is still not resolved and/or noticed.

It would be great if NGG wouldn’t alter a theme’s code and instead would use a hook for this kind of functionality.

In my opinion a simple warning would be enough. Someone who leaves out wp_head() and wp_footer (on purpose) should know how to handle the consequences ??

Seems like NGG is searching for the closing </head> and </body> tags.
If I put a space before the closing bracket (</head >) it doesn’t detect the tag correctly and doesn’t auto-inject wp_head() & wp_footer()

Edit: Found the culprit… it’s class.photocrati_resource_manager.php, function name is move_resources(). It doesn’t check if there is a wp_head() and/or wp_footer().

Additional info: Yes, we are aware that leaving out wp_head() & wp_footer() can lead to serious incompatibilities with many plugins.

Yes, I am aware of that ?? thanks for the effort all the more!

For my work it is not really essential to upgrade to 3.3, so I can wait.
I just wanted to give this problem a place to be solved or even just to share each others bugfixes.

If I can take the time I will look further into the occurring problems. For now I’m just a silent reader Qian’s forum ??

This is awesome, thank you. Hope it’ll get into the official plugin soon!

EDIT: Just tried it, unfortunately it doesn’t provide full functionality.

Mainly my post was to “poke” the plugin author ?? the problem occurs on all the WordPress 3.3 installations since the editor was altered in 3.3 (read more: https://wpdevel.wordpress.com/)