wickedplugins

Hi @saiftheboss7,

I apologize for not responding to this earlier; for some reason I didn’t receive an email notification for this thread.

I believe this should be fixed in the latest version of the plugin (2.17.9) but if you still have trouble, please let us know.

Also, if you happen to have a chance and are able to look at the value of the timezone_string setting that is in your database’s wp_options table, I’d be curious to know what it is as that might shed some light on what originally caused the issue. If you’re not able to look in the database, could you let me know what timezone you have selected on the WordPress General Settings page?

Hi @edusachs,

Can you provide some more info on what’s happening?

Here are a couple things you could check:

• Make sure the folder pane is toggled on by clicking the “Toggle Folders” link near the bottom of the left-hand navigation
• It’s possible that there is a conflict with another plugin. You can check by temporarily deactivating all other plugins and seeing if the issue goes away. If it does, re-enable the plugins one-at-a-time to determine which plugin is causing the conflict

Hi @descomputers,

I apologize for not responding sooner but for some reason I didn’t receive an email notification about this thread.

Our plugin doesn’t use the eval function anywhere; however, our plugin does rely on several other scripts shipped with WordPress including jQuery, various jQuery UI scripts, Backbone, and Underscore. My guess is that perhaps one of these other scripts uses the eval function.

I’m afraid this isn’t something we can fix on our end since we don’t have control over those other scripts.

Hi @bash88,

We have it set to false to prevent pages on the front-end being available for the folder terms.

We’ll definitely consider adding this as an option. In the meantime though, you can also make the taxonomy public by adding the following code snippet to your theme’s functions.php file and changing the taxonomy name:

add_filter( 'register_taxonomy_args', 'custom_register_taxonomy_args', 10, 3 );

function custom_register_taxonomy_args( $args, $taxonomy, $object_type ) {
	if ( 'wf_page_folders' == $taxonomy ) {
		$args['public'] = true;
	}

	return $args;
}

I hope this helps! I’m going to mark this as resolved but if you still need help or have questions, feel free to add additional comments.

Hi @lshr,

I’m afraid there isn’t a way to do that with our plugin.

Based on your example pathnames though, that looks like something you may be able to accomplish with custom taxonomies. You could also structure your page hierarchy that way to get those pathnames. Or, another idea would be to use a plugin like Custom Permalinks.

I hope this helps!

Hi @ofmarconi,

Just following up to let you know that this has been fixed in version 2.17.6.

Thanks again for reporting the problem and please let me know if you have any other issues.

Hi @kondorljano,

Thanks for reporting this. What is the URL in the browser when you get this error? Would it be possible for you to send a screenshot showing the entire screen?