MacRamsay

I second this issue, finding same problem on all sites with WooCommerce and CF7…

I second this issue and look forward to the update.

Thanks!

I’ve now discovered that it’s a clash with the ‘Jigoshop Video Links’ plugin I installed fairly recently (It wasn’t brought to my attention that this issue was going on for so long!).

I’ve no deactivated it and seems to be working fine. I’ll report it to JigoShop support and see if they can sort the plugin clash out.

Brian

Thanks for looking, I’ve checked, re-checked and tried all sorts of combos and activations/deactivations to get it to work – it’s still either all menus or none, even though the menu locations are listed in the RSM plugin options…

I get the same problem. I’m trying to use the menu selectively. There are lots of mentions of calling the WP nav menu properly with a location, but I’ve tried this and still had no luck.

I’m using in my theme: <?php wp_nav_menu( array('primary-menu' => 'Primary Menu' )); ?>

And I can turn this location ‘on’ in the plugin options, but don’t see the results. It’s either all on, or all off at the moment – nothing selective…

I’m getting this message too… It may be a core WP files, but it’s only come up since i upgraded FSCF.

You are a genius, ipstenu, you saved my bacon. Thank you so much for the rapid response tip.

Thats strange – i looked to see if my ‘allow users to create new users’ option was checked, and it was – every time i un-check it and save changes, the page reloads but the box is checked again? Any ideas why it wont let me turn this option off?

Thanks thanks thanks everyone!

I was just about to finish writing another entry here, when, as if by magic, it worked. Brilliant, but why?!

Here is my final .htaccess file:

RewriteEngine On
RewriteBase /mybag

#uploaded files
RewriteRule ^(.*/)?files/$ mybag/index.php [L]
RewriteCond %{REQUEST_URI} !.*wp-content/plugins.*
RewriteRule ^(.*/)?files/(.*) wp-includes/ms-files.php?file=$2 [L]

# add a trailing slash to /wp-admin
# RewriteCond %{REQUEST_URI} ^.* /wp-admin$
# RewriteRule ^(.+)$ $1/ [R=301,L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule . – [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-.*) $2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
RewriteRule . index.php [L]

<IfModule mod_security.c>
<Files async-upload.php>
SecFilterEngine Off
SecFilterScanPOST Off
</Files>
</IfModule>

I have two separate files, the above one in the wordpress install and a simple redirect file in the server root.

All is good now, but who knows why it suddenly worked… I didn’t really change anything, only attempted something and after it didnt work, i returned it to previous state and it worked! V.ODD

Spoke too soon… they’re in again… damn sploggers.

These lines in my .htaccess (in the server root directory) are causing a 500 server error, so i currently have them commented out:

# add a trailing slash to /wp-admin
RewriteCond %{REQUEST_URI} ^.* /wp-admin$
RewriteRule ^(.+)$ $1/ [R=301,L]

I was wondering:

Should i have a .htaccess file in my server root folder to provide the re-direct, and ALSO have a separate .htaccess file in the root of the WP installation? Can you have two?

That way the file in the root of the installation should work the same as any other installation (rather than a sub-directory install of WP).

Resorting to crazy tactics here!

I’m pretty sure its not windows server, im hosting it on Dreamhost shared server and i think they use Linux servers(?). That’s that idea out the window then!

I currently have that line commented out (and so inactive) with a # at the beginning of the line – the redirect no longer works, but the site still has the same issues…