[SOLVED] Slideshow Cutting Off Images
 

I'm currently TRYING to use the NextGEN Gallery to insert a slideshow into a page. I'd post this issue on the NextGEN Gallery support forum, but they're obviously having serious problems over there. Nothing is getting answers, there are so many posts. So, here goes.

Like the Subject says, the Gallery is the NextGEN Gallery by Photocrati. However, I had similar issues with the Slideshow and the SliceShow plugins. So I'm thinking the problem may indeed be in Atahualpa (ouch!).

Problem: Images are cut of at the bottom, and the container even resizes for the truncated images. It's somewhat random, some display normally, others get truncated and the container resizes to fit. I can't detect a pattern. Same issue in multiple browsers.

What I did to troubleshoot:

1. Tried other display options in NextGEN (different effects--fade, slide, etc.). Using the Flash slideshow is NOT an option for my site.
2. Disabled ALL other plugins.
3. Replaced NextGEN Gallery with Slideshow and then SliceShow--had similar issues.
4. Re-activated NextGEN Gallery and ALL other plugins that I needed, but changed theme to Twenty-Thirteen theme, and the problem disappears completely.

I'm left to conclude that there's a conflict between Atahualpa and the NextGEN gallery (as well as some similar plugins).

Any help would surely be appreciated.

Thanks.
Jack

Version of atahualpa and wp?
What is the ulr of a page displaying the issue?

Atahualpa 3.7.12
WP 3.6.1
http://test.culinarymgmnt.com/faulkner/cafesiena

Something is even keeping the page from rendering completely.

Jack

everything looks fine to me. what isn't rendering?

btw this image gets a not-found

I guess I'll take a look from another computer. Thanks.
Now I have a DIFFERENT issue, but I do see a pattern and it may be a consequence of the URL rewriting that I'm doing. Did you happen to browse any other pages? The /faulkner in the background image URL only appears on pages that have /faulkner in their URLs. All pages at the server root directory level have the correct background image. Pages that appear (due to URL rewriting) at a second-level (like /faulkner) have a broken URL for the background image, and I suspect other custom images.

I suspect I could work around this be changing the "/" characters in the URLs to something else, but I was hoping to use the URLs as they already are.

Is that clear as mud? Got any input for me?

Thanks.
Jack

You're right, clear as mud. Where are you doing the rewrite and why?
What happens if you don't do the rewrite?

I'll try to give examples, rather than explain.

The folowing pages work properly--that is, the background image works fine:
http://test.culinarymgmnt.com
http://test.culinarymgmnt.com/about-us
http://test.culinarymgmnt.com/food-services
http://test.culinarymgmnt.com/faulkner

Their background image is at
http://test.culinarymgmnt.com/wp-con...background.gif

The following pages have a broken URL for their background image:
http://test.culinarymgmnt.com/faulkner/cafeteria
http://test.culinarymgmnt.com/faulkner/grille
http://test.culinarymgmnt.com/faulkner/cafesiena
http://test.culinarymgmnt.com/faulkner/coffeecup

Their background image URL is
http://test.culinarymgmnt.com/faulkn...background.gif (same as the others, but with /faulkner added).

By "rewrite", I'm just referring to how Wordpress gives the option for pretty URLs, search-friendly URLs, or whatever they call it. Oh, "Permalinks" is their term. It uses Apache's mod_rewrite to do this.

Why do I rewrite the URLs? I like it to appear that they're in a directory hierarchy, as they would in a non-Wordpress, static-page setup. That, and I'm anal OCD, I guess.

Jack

And to answer your last question, I just tested it. It works properly using WP's default permalink configuration.

So, in conclusion, using a / in a page's permalink will cause Wordpress to generate an incorrect background-image URL. I doubt this is a theme-specific issue, more likely global.

Jack

I'm not sure what I've done to break this, but now NONE of the pages have the correct background-image URL except the "main" page.

And, I did not add the /faulkner to the Permalinks. It's apparently done automatically because they're "child pages" of the /faulkner page.

Jack

Use a full path for the background image instead of a relative path.
instead of

You lost me there.

The background image location is specified in the Atahualpa Theme Options | NEW Image Locations. It says "Base directory for images. No leading or trailing slashes. If the 'Relative location of header images?' is set to 'atahualpa' this option is ignored and the default Ataualpa folders will be used."

Jack

I may have a browser issue. The page source shows the background image in the same place on all pages now:But for some reason, the background is not showing in my browser. The odd thing is, the favicon and logo ARE showing up.

And when I look at the given URL for the background image:
http://test.culinarymgmnt.com/wp-con...background.gif
It's there.

I'll just check from another computer.

Jack

Just verified, same issue with Safari on the iPad.

It baffles me because when i view the page source, the background-image URL is CORRECT and it's the same one as on the site's home page, which DOES display.

Off to look at httpd logfiles, to see if it's throwing 404 errors...

Jack

The httpd logs tell all. Apache logged the following GET request when I went to http://test.culinarymgmnt.com/faulkner/

I don't recall this behavior on any of my other Atahualpa sites.

Jack

Okay, fixed. But I'd cal it a workaround. I went back to Atahualpa Theme Settings | Body, Text, and Links. Changed the background-image to a fully qualified URL as lmilesw suggested. That works, but in my opinion, it's a workaround for something that's inherently broken. It's something that won't be portable when I move this out of "test" and into "live" status.

Thanks for the help.

Jack

I just noticed something else in your syntax which may preclude having the full path. There is a missing leading slash to your relative path.

You showed
It should be

Most definitely! When you first made the suggestion about using the full path, I didn't know what you were referring to. I thought the line of code you cited was generated by Atahualpa, based on Atahualpa Theme Options | NEW Image Locations.

But I'm fairly certain you're correct, and I'll go back and try that. Using relative paths has never been a problem on my other Atahualpa sites, so that must be it. Yep, just confirmed it.

Sometimes the simplest little mistakes are the hardest to identify. Thanks for the help.

Thanks.
Jack