jatacid

Sure is,
The menu items are the edit links already!
All you need to do is click haha.

It’s default an edit link, with extra option to view only.
Though you’re right, maybe I need to make it a bit clearer like with a hover title or something.

Cheers!

Haha yeah, well, that way you’ll make it much wider too ??

I’ll start looking into how I can change the encoding of it…Bit of a mystery this one for me!

Hi Craig,

Thanks for the feedback!

1.08 has a new setting field where you can label it whatever you like ??
Call it ‘WordPress Eats Eggs Everyday’ if you want haha.

1.08 also combined the old ‘View’ and the ‘Edit’ lists into one menu because usually you only need one action or the other on a page so the tiny extra mouse movement to see the ‘edit’ submenu wasn’t an issue. Give it a try – once you get used to it, it’s actually a lot easier for muscle memory to find and then edit a page.
I’m gonnna see if I can add a highlight colour to the current page too so it will be even clearer.

Good point about it being too narrow though! I’ll definitely throw that a bit wider in to the next version.

RE: the question marks you’re seeing – you don’t have any ‘hypens’ in your title by chance do you? A couple of users have reported it but I think it might be a character encoding issue I’m not sure. They’re like little quesitonmark triangles right?

I’m gonna go ahead and close this Daniel as it will be done in a future version. Thanks for the heads up!

Thanks Daniel,
I’m doing a bit of work to make it easier to add more settings so the hiding of default nodes will be in a future release ??

As for your idea about ‘remove_action’, I tried it but for some reason it wasn’t working. I don’t think there’s anything wrong with my syntax?

Cheers!

Hi guys,
I found the syntax error on one of my really old sites. It has to do with the version of PHP running I believe.

I broke my syntax apart a little more and it is now fixed in v1.05.

Cheers for the heads up!

What version of php are you guys running?

I can’t replicate the issue, but if you can go into your plugin files with a file editor or FTP and change the following to test it for me.

Change from:

//Adds a "Edit Page In BB" menu to adminbar
if (get_option('apspider_radio_bbmenu')[0] == 'option1') {  // Checks if option is set to Display
	add_action( 'admin_bar_menu', 'apspider_edit_bb_pg', 999 );
}

Change To:

//Adds a "Edit Page In BB" menu to adminbar
$apspider_is_turned_on = get_option('apspider_radio_bbmenu')[0];
if ( $apspider_is_turned_on == 'option1' ) {  // Checks if option is set to Display
	add_action( 'admin_bar_menu', 'apspider_edit_bb_pg', 999 );
}

Let me know if that works – I’d appreciate it.

Cheers,

J

Ah interesting!

I wonder if you could do a catch into a cache file and then put it into memory after the time has passed?

Hi @jenjohn,

Yeah good support. But that’s so bad of them to disable a core functionality like that. New server environments should only be applied for new customers only imo.

Kick up a chat with support.
They added a snippet of code to my .htaccess file which bypasses the mod_security component that they changed.

I asked him if it would be possible to copy paste the code to my other sites but he said ‘be extremely careful because it may be a different number on a different site’s environment – it’s better to chat to us for each site’.

So naturally, I tried it on one of my other sites and it fixed it fine. Use at your own risk:

# Added by Siteground Support Team
<IfModule mod_security.c>
SecFilterRemove 001838
</IfModule>

Hi @jenjohn

I just recently started experiencing this same issue and wondering what server host you are with?

Not Siteground by chance are you?