fleetadmiralj

OK, an update: it works properly in Internet Explorer, Safari (Mac and PC), Firefox (PC, didn’t test on Mac cause my Mac hates FF), and Chrome on PC, which DOESN’T have the ScriptNo extension…

So I disabled it in Chrome on mac and…voila…it works properly. So apparently even though it SAYS it’s it’s trusting all the scripting and stuff on the site, that plugin is apparently still interfering with the site enough to muck up that redirect functionality. OK, nevermind, nothing to see here…

OOOOOOK, I did a little fix. In the lightbox-gallery.js file, I changed

jQuery(‘.gallery a’).tooltip({track:true, delay:0, showURL: false});
jQuery(‘.gallery1 a’).lightBox({captionPosition:’gallery’});

to

jQuery(‘.gallery dt a’).tooltip({track:true, delay:0, showURL: false});
jQuery(‘.gallery1 dt a’).lightBox({captionPosition:’gallery’});

That’s telling it to ONLY grab the a tags under the dt tag (where the image is anyway). This fixed it so that I could put a link in the description and have it work.

Aha…I figured out the problem. I had a link in the description of the first item, and that was messing it up.

It’s hitting the “else” in the if-else statement because it’s the first image (and thus i < 1 in the encompassing for-loop). However, when it’s adding items to the array, it’s grabbing the URL of the image to grab like this:

jQuery(jQueryMatchedObj[i]).parent().parent().children().children().attr(‘href’)

Now, I don’t know where the two parent()’s are coming up form but I assume they are getting you to appropriate “gallery-item” dl. The first child gets you down to dt/dd under that (since it’s grabbing all children), and then the next child goes to the a tag (with the image link) under the dt, and the caption and description spans under the dd. It then grabs anything with an “href” attribute from those three items.

However, since I had a link in the description, it not only grabbed the href from the image a tag in the dt, but it grabed the href from the link I added to the description, and viola, it added two items at once, one of which was not a link to the image, which blew the code up.

This isn’t a fatal problem – I guess I can just put the text of the link in the description without having the actual link there (unless I can figure out a fix to temporarily go there) but I think it might be better to attempt to reference that dt a tag specifically. I certainly don’t think it would be too difficult to grab the “href” items from the dt instead of from the dl. I do think being able to put in a link into the description would be a useful thing to have.

I don’t know if this is the problem the original person was having, but this is the problem I was having.

Well…I think I’ve gotten the problem more or less narrowed down to the _start function in jquery.lightbox.js, specifically the if-else statement between lines 89 and 96.

From what I can tell, it’s loading the initial array incorrectly, so that the transition between the first and second image in the gallery is breaking. Specifically in my case, it’s trying to load the URL associated with the first image as the 2nd item in the image gallery. All other images appear to load up fine (for example, I can click on the 2nd image and proceed through the rest of the gallery just fine).

For whatever reason, it’s hitting the “else” part of this code for the first image and the “if” part for everything else. I just haven’t figured out why yet…

I had a similar problem with the header on twentyeleven. The solution for that was to set the z-index on the branding item to z-index: 1 and set the z-index for the gallery to something like z-index: 1000.

You’ll need to edit the theme/plugin CSS directly (not recommended) or create a child theme and insert the CSS changes into the style.css file in the child theme.

Given that something in the sidebar is on top of the lightbox, something probably has it’s z-index set to something high in the theme CSS so you’ll probably need to poke around to see what might have a high z-index and then change it to a lower level.

I hate to revive a dead thread, but I’m also having this problem. I’m using WP 3.3.1 and whenever I click “next” or “prev” all I get is the spinning icon and the new image does not load.

I would love this plugin to work as it does exactly what I want (shows the image DESCRIPTION in the lightbox AND uses the native gallery functionality of WordPress) but it’s pretty useless if people can’t get from one image to the next.

Unfortunately, I agree with Chip that any solution has to be altering the templates, either Twenty Eleven’s templates or by creating new versions of those templates in your child themes, or by commenting out/deleting the function in the twenty eleven functions.php file.

While many of the functions in twenty eleven come with a “if function exists” check, twentyeleven_comment_nav does not, and has been noted, just creating that function over again will cause an error, and there is no way to copy over it since the function is called directly from the templates.

So for the meantime, one will have to make some changes that probably shouldn’t be necessary if the twenty eleven template had been coded the way it probably should have been to start with. Hopefully it’s something they will address sometime in the future.

oooooooook. I think I figured out the problem. I haven’t confirmed it in the sense that I 100% know this is the reason, but this is what fixed it:

I think the “long description” for my theme (ie the thing I put in the style.css file after “Theme Name:”) was too long.

One thing I noticed was that in the db cells which said what menu to use – the mods_the_long_theme_name items, the theme name I was using was getting truncated, so it was like “mods_a_really_long_theme_na” When I changed it so that the whole thing fit….the menu worked.

OK…more into the deep bowels of the database, because I wanted to see what it was doing, both when it worked (using another theme) and both when it wasn’t. As far as I can tell….nothing is different.

in wp_##_terms, it has:
term_id: 6
name: Main Nav
slug: main-nav

in wp_##_taxonomy, it has:
term_taxonomy_id: 6
term_id: 6
taxonomy: nav_menu

(at first I thought the taxonomy name of nav_menu vs. the slug main-nav might be the problem, but it didn’t cause a problem when showing the nav on the template that worked)

in wp_##_options, under mods_the_long_theme_name it has:
a:1:{s:18:”nav_menu_locations”;a:1:{s:7:”primary”;i:6;}}

so it appears to be using the right nav (note i:6, which changed when I at least attempted to select the menu), so it appears to be updating things in the database just fine. It just…isn’t working.

I haven’t changed anything in the header, and the header.php file this in it:

<?php wp_nav_menu( array( ‘container_class’ => ‘menu-header’, ‘theme_location’ => ‘primary’ ) ); ?>

(but it’s obviously working since it worked when I used another theme).

Again…any ideas why just creating a new theme would blow it up?

OK, I changed the child template to one I had created before, added the menu..and it worked. Switched it to another child template, the menu choice disappeared, but it seemed to stick when I selected again (now that I remember, I think this was the problem with the menu before – it would get wiped out when I changed the theme). Switched to the new template…menu won’t stick.

I may try just wiping out the template and trying again, though I don’t really know why it won’t work with this child template I made today.

OK, I’m starting to think this isn’t an “error” though it is kind of misleading to me.

If I created the user without checking the box, they get sent an email with a link to activate their accoun. But if I do check it, they get an email, but don’t have the confirmation link, and it looks like it “activates” the user automatically. That means this functionality that I want might not be built in in the first place.

That brings me to the next question: are there any plugins that will prevent the email from being sent at all (that work). I already noted one I tried above that didn’t really work too well. I know there are a lot of plugins that cut out emails sent to the admins, but I want one that eliminates the emails to the users as well, if possible.

Thanks.

Hmm. Deactivated all the plugins, and my test user is still getting the “welcome” email address, so it doesn’t look like it’s a plugin problem.

OK, I tried installing a plugin that eliminated sending the email out (called Eliminate Notify Email) but I soon found out that didn’t work as, aside from not sending out the email, it also didn’t add the user to the site I was adding them to so…that’s out the window.

Any other ideas? Or plugins that might work?

Just to quadruple post before someone else come in here again…

The answer to my last question is…”yes”

I added them to site #1 as an admin, put in their site in as the dashboard site, then put the other site in as the dashboard site and viola, he was removed as an admin of the first site and added a subscriber to the second.

So that appears to explain all of the problems I was having. And all because I didn’t know what I was doing lol. Thanks.

Additionally…actually reading the note under the field (amazing what happens when one actually reads what things are for and do!) it looks like that might explain the people being added to subscribers.

One final thing…I had set the blog in question #1 as that blog before switching it to the other blog in question. That person was an admin and not a subscriber (and it says it moves SUBSCRIBERS of the old blog if you change it) but could that possibly even explain why they were taken off as an admin for the first blog?