dylanjameswagner

Thank you @danielbachhuber

I definitely had tables with capitalization. Perhaps from an earlier version before a recent update. The “Delete Wordfence tables and data on deactivation” feature definitely didn’t work when there were tables with capitalization because of the same error described in my original post. Eventually I found the right combination of deactivating/activating the plugin and manually deleting the “wf” tables.

It appears as the the Wordfence plugin has had troubles creating SOME of the tables it needs. And there seems like table name capitalization may perhaps be part of the issue.

I have been able to get it running as expected but it is not clear which steps of activating/deactivating the plugin, and/or saving settings has sidestepped the issue and allowed the tables to be created.

I have found this error as well. I think the OP was on the right track, there are references to both ‘help’ for ‘helper’ in the plugin, perhaps one is incorrect?

tribe_dynamic_help_text
tribe_dynamic_helper_text

The issue is not resolved if the plugin ships with a script error.

I found this as well and submitted a GitHub issue that hasn’t been addressed. Copied the content of the issue below.

https://github.com/jakemgold/simple-page-ordering/issues/6

In the admin. When viewing a custom post type list by taxonomy the Sort by Order link is invalid, it includes an encoded ampersand, outputting #038; where an ampersand should be.

I believe the issue can be traced to line 284 of simple-page-ordering.php. There is a remove_query_arg wrapped by esc_url which I believe is encoding a trailing ampersand once the orderby and order` have been removed.

I am able to restore expected functionality by removing the esc_url, but I am unsure of the security issues with doing so.

Since this is for admin screens I would think the risks would be low.

I have used the technique of “zooming out” the page to make it easier to drag and drop a log list.

CTRL + - (minus) – Win
CMD + - (minus) – Mac
CTRL/CMD + 0 – (zero)

I did some further searching and found this post and ticket.

I managed to come up a this solution to re-enable the editor.

/* enable page_for_posts editor */

function custom_edit_form_after_title($post){
	if ($post->ID == get_option('page_for_posts')) :
		add_post_type_support('page','editor');
	endif;
}
add_action('edit_form_after_title','custom_edit_form_after_title');

I have been doing the same thing. Annoyed that this has changed.

I have been experiencing the same thing since I updated to 4.2.

Awesome!

Does anyone know if this information is passed to PayPal?

I had considered this, but couldn’t think of a good class name since .list-pages was already being used. I think your solution works to solve that and retain clear backward compatibility.

Thanks Ben for hearing me out, hope to see this in a future update!

Great. ??

Sure thing. I just tested this with my current project.

I link to a theme wide script file loaded in the footer.php just before the </body> tag, but before wp_footer(). Idk if the location matters, but it is working for me there.

<script src="<?php bloginfo('stylesheet_directory'); ?>/-/scripts/custom.js"></script>

In this script file I have only jQuery. Here is the whole file with the only the relevant parts.

/* custom.js */

jQuery(document).ready(function($){

/* other non relevant jQuery, removed for this example... blah blah blah */

/* plugin contact form 7 */
/* hover effect broken in update - last checked in version 3.6 */

	$.fn.wpcf7NotValidTip = function(message) {
		return this.each(function() {
			var into = $(this);
			into.append('<span class="wpcf7-not-valid-tip">' + message + '</span>');
			$('span.wpcf7-not-valid-tip').mouseover(function() {
				$(this).fadeOut('fast');
			});
			into.find(':input').mouseover(function() {
				into.find('.wpcf7-not-valid-tip').not(':hidden').fadeOut('fast');
			});
			into.find(':input').focus(function() {
				into.find('.wpcf7-not-valid-tip').not(':hidden').fadeOut('fast');
			});
		});
	};

}); // .ready

Maybe you didn’t have the opening jQuery ready function? The rest of the code I believe is directly copied from the code above.

On my site, once I included this in the script the fade-away-on-hover effect works. If i comment it out to test that functionality goes away.

I intend to check from time to time to see if the original plugin functionality resumes working and then I can remove this code from my theme script entirely.

Hope this helps, if not we I can try to help again. ??

I copied this into my site specific script file, not into the plugin directory script. Worked just fine. I also noted the last version this functionality was check in and didn’t work for future removal.

Thanks for posting. ??