Bug Context menu doesn't work in main instance, but does in instance2

[teach1st]

I lost context menu ability in my main vbshout instance, on different vb pages, in different browsers, and on different computers and operating systems (windows, mac, ubuntu). Clicking on a user name results in no action. I tried the default skin, disabling other mods, repairing cache, repairing and optimizing tables, and everything else I could think of. Context menu does work in instance 2 (which is in my arcade), and when I tried replacing instance1 with instance2 on my forumhome, I had the ability to use the context menu.

So, I tried to replicate the settings of instance 2 in instance 1. I KNOW that context menu is enabled in both. No matter what else I change in instance 1, I can't get context menu back. (I did not replicate some of the size or timing options.)

I know other mods and template changes can interfere, but Instance 2 works in the same environment and template where instance 2 fails. I use shout with students and need as much immediate control as I can get. I know I could just put instance 2 in forumhome, but I'd like my main instance to work. Any ideas?

 

[Fillip H.]

Are you sure you enabled both the global switch and the per-usergroup switch in instance 1?

 

[teach1st]

Thanks for your prompt reply. I'm not sure what you man by global switch, but I'm pretty sure all settings are correct. I hadn't messed with settings prior. The per usergroup is set and the instance permissions are on all for admin.

The only category checked no in instance permissions is "auto idle" and it is no for both instances.

 

[Fillip H.]

Above the usergroup permissions in the Instance Management, there's a switch that fully disables context menus. "Enable Context Menu This will allow you to globally disable the advanecd context menu when clicking on a member's name in the Shoutbox.
Enabling the context menu adds a large amount of data to each AJAX request, but enables quick access to member and moderator actions."

 

[teach1st]

Yes, the global switch is on in both instances. I tried running with it off in the offending instance 1 and then switching it back on, but it didn't make a difference except that I get linked to a user profile when it's off.

 

[Fillip H.]

What happens if you create a new instance (3) with duplicate permissions and settings to 1 and 2, and then put it on the front page along with 1?

 

[teach1st]

Context menus work in the third, new instance. When I click on a user name in instance1, the context menu opens in instance 3.

If it would make it easier, I have an admin user name and password for you. Want me to PM the login info to you?

 

[Fillip H.]

Aha, that is an entirely different issue, one that will be fixed in an upcoming bugfix release. I already have the fix on my dev machine

 

[teach1st]

Context menus work in the third, new instance. When I click on a user name in instance1, the context menu opens in instance 3.

If it would make it easier, I have an admin user name and password for you. Want me to PM the login info to you?

Let me change that. If I run instance 1 first, the context works in instance 1. Clicking on instance 3 opens the context in instance 1 (the top one)

If I run instance 3 first, the context works in 3. Clicking on instance 1 opens the context in instance 3 (the tope one)

So, if I run instance 1 first, and then run instance 3, the context works in instance 1.

 

[Fillip H.]

Like I said above, that will be fixed in the upcoming bugfix release

 

[teach1st]

Aha, that is an entirely different issue, one that will be fixed in an upcoming bugfix release. I already have the fix on my dev machine

OK. So, I just sit tight and wait for the update.

 

[teach1st]

Thanks so much for your prompt help, Fillip H.!