cnymike

Yes I agree that the previous positive ratings are not reflective of the actual current state of affairs. I just “upgraded” and had most of my galleries disappear.

I have given up on NextGen.

Just had this problem and just tried the “fix.” Solved the problem.

Is this a deprecated way of assigning that or what exactly is incorrect with the original code? Just wondering so I can let the theme developer know… and to avoid ever using that theme developer again.

Holy moley… I’ve just wasted about an hour with this same issue. I’d drag the subpages into positions, save, and they’d all snap back to toplevel position.

Read this post and changed my browser from Chrome, to Safari and in Safari I was able to create the sub-menus. Go figure.

Chrome was the culprit… but why?

@michael Torbert I am glad to hear that. Have verified what you say so thanks for the clarification.

As a follow-up, here is the link from Google specifying where the analytics code is to go.

https://support.google.com/analytics/bin/answer.py?hl=en&utm_id=ad&answer=1008080

@danieldeceuster Totally in agreement with you. The code snippet should be placed right before the closing head tag as stipulated by Google. I will not use this plugin because of that.

I’ve not seen many themes that offer flyout dropdown sidebar menus. Nor are there many plugins for that and the few that I have run across are not rated very highly. I’d like to hear some specific recommendations if you have any.

Add me to the list of people who’d like to have the ability to add a fly-out dropdown menu to a sidebar menu.

It’s very odd to me that this very common feature of most other CMS’s isn’t readily available in WordPress. I guess the functionality is sort of there with custom menus and if you know how to code. But I don’t know how to code.

Good news. Here is the response I got from Jetpack support.

“Thanks for letting us know about this conflict. ?We will include a fix
for this in the next version of Jetpack, which will probably come out
in a few weeks.

In the meantime, you can have Jetpack active without loading Jetpack’s
shortcodes. ?Install and Activate Jetpack, then go to your blog’s
admin -> Jetpack and click the “Learn More” button on the Shortcodes
box. ?Then click the “Deactivate” button that appears.

Obviously, that’s not an ideal solution since it disables *all* of
Jetpack’s shortcodes, not just the conflicting one.”

Yes, it is slightly easier. (I did not test it either.) However, as with the NextGen hack, it will also be overwritten during any subsequent Jetpack update until a permanent fix is implemented.

So now we have two hacks, one that works and one that -may- work from which to choose so that we can temporarily fix the problem.

It’s a start.

I have in fact just emailed Automattic from their contact us form to notify them of this apparent conflict between NextGen and Jetpack.

I have also used the link that Justin Tadlock provided to contact Jetpack support directly.

Anxiously awaiting a reply .

And I apologize for my misspelling of Automattic.

No I have not personally asked Automatic to modify their code.

Previous posts regarding this issue have implied that Automatic was made aware of this issue though.

I’d be happy to notify Automatic. What do you suggest as the most reliable way to do so, so that someone will actually acknowledge that there is an issue?

Well perhaps they should fix their code.

But in a situation where they haven’t, then I would think it would be helpful to all of us that use Jetpack and NextGen, to modify NextGen.

But I guess that’s your prerogative to leave it as it is and let users have to hack your code so that things work with Jetpack.

Here is a link to another thread that offers a simple hack to fix the incompatability between Jetpack and NextGen.

https://www.ads-software.com/support/topic/plugin-nextgen-gallery-shortcode-slideshow-conflicts-with-jetpack-by-wordpresscom-plugin?replies=8