Home › Forums › Weaver and Plugin Interaction › Weaver Xtreme and NextGEN Images
- This topic has 7 replies, 4 voices, and was last updated 7 years, 10 months ago by RonCharest.
May 12, 2015 at 18:57 UTC - Views: 4 #17747
I just converted to Weaver Extreme and in testing out my existing posts noticed a change in behavior with thumbnails. For any photos I use in my posts I first load them into a NextGen photo gallery, and then select them into my posts using “Add Media / NextGen Gallery” options as thumbnails. Previously, those images would be links to the larger image and pop-up when the thumbnail was clicked. Now with Weaver, those thumbnails do not work the same. Is this a bug, or am I doing something wrong…?ThanksMay 13, 2015 at 08:20 UTC - Views: 3 #21935GillianModerator
Saying “those thumbnails do not work the same” does not describe the issue you have – can you be more precise? A link to your site, as explained in the Forum Guidelines, would also help.Just curious – is there a particular reason you are uploading your photos into a NextGen Gallery, rather than just into the Media Library? Perhaps you are using the Gallery elsewhere on your site?
May 13, 2015 at 11:15 UTC - Views: 3 #21936
Gillian,Here’s a link to a post as an example:Actually, of the six images in this post, one is still clickable, and I cannot figure out why. There is no difference in how this one was embedded vice the other five. In my previos Theme, all six thumbnails were clickable and would open up to a larger image that floated over the post.I have over 1000 photos on my site and adding more all the time. I’ve chosen to link directly to my photos as a way of minimizing redundant images, when I’m using pics specificto that post. I do use the Media Library for clip art that I expect to reuse in future posts. For the amount of photos I have, I really need a higher-end package like NexGen to manage my collection.ThanksMay 13, 2015 at 11:41 UTC - Views: 3 #21937
Update: I just changed themes as I discovered that all my static pages had become corrupted using the Weaver Xtreme theme. In all static pages (I have about 50) right sidebar information was being displayed on top of the page content, again on the bottom under the content, and on the right sidebar as it was supposed to be. Pages content includes NexGen photo galleys, my archives (built with some third-party plugins that enable short codes) and just various stories I’ve chosen to built into static pages.I like the Weaver layout and posting options, but I cannot use it if it corrupts my content like this.May 13, 2015 at 13:20 UTC - Views: 3 #21938scramblerModerator
I am not sure how the theme could do that, @weaver can confirm
A possibility is that you have HTML errors in your pages. these will causes random layout break depending on the browser or the structure of the page (which is why it could show up after changing theme)
You should run your pages through the HTML validator and look for Open closed tag errors, which are the main cause of layout breaking upMay 13, 2015 at 14:46 UTC - Views: 3 #21939
Thanks Scrambler,I’ve had HTML problems before that affected my page layouts using the “Chiron” theme (which I’ve now gone back to). But I think those have been cleared up. I will check to be sure I don’t have any problems not showing up in Chiron.May 13, 2015 at 17:28 UTC - Views: 4 #21940WeaverKeymaster
Just a note: there no known way Weaver Xtreme (or any theme, actually) can “corrupt” static page content. (And corrupt is a really scary word to use. Perhaps break the page layout is a better term?). And the latter phrase really describes what has to be going on.
Weaver Xtreme has a very solid HTML structure, but because of a number of factors, especially those related to getting sidebars to display elegantly on mobile devices, even the most trivial HTML error can break content / sidebar structure. This can be errors introduced in the content (missing or extra <div>s are the most likely culprit), or there can be plugins that generate incorrect HTML – this is not that uncommon, believe it or not.
So, before thinking Weaver is “corrupting” your pages, try to find the HTML error. Since it is happening on every page, it is likely something in a widget in your sidebars. The easiest thing might be to start by moving widgets one at a time to the inactive widgets block.May 15, 2015 at 14:35 UTC - Views: 4 #21941
Thanks Weaver. I’ll check it out.
- The forum ‘ Weaver and Plugin Interaction’ is closed to new topics and replies.