Home › Forums › Weaver Show Posts & Show Sliders › show slider won’t show a slider at all on my site
- This topic has 13 replies, 3 voices, and was last updated 10 years, 11 months ago by
Qoheleth.
-
AuthorPosts
-
September 21, 2015 at 17:28 UTC - Views: 4 #18284
Qoheleth
ParticipantI’ve been using Premium Featured Posts Slider for my home page and it works, but I’d rather use Weaver Show Sliders. (It has more and better options and it’s free.) However, I can’t get the slider to show up at all. I created a Show Posts filter for my Featured Items posts. It works fine, displaying the posts I want in the order I want, but a slider using it as a filter doesn’t show up. I’ve also tried entering Weaver Slider Posts matching my original posts and using either a slider group or the atw_slider_post type. None of it works. I’ve tried inserting the shortcode into the premain injector and tried it in the body of the page content as well. Neither work. I do notice that the height of the element (as shown by Inspect Element) is 0.Any help would be appreciated.The test page is http://www.disciplesnet.org/test-page/September 21, 2015 at 17:34 UTC - Views: 3 #24656scrambler
ModeratorFirst we need to check what options you used for the slider.
If you are making a post slider based on a filter double check the options below.
Slider options > Slider Content should be “Show SLider as post”
Slider options > Slider Filter should have your created filter selected in the drop down list. SLider post slug below should be empty.
Save the options.
Then create a test page that has nothing in its content box except the slider shortcode, and give us a link to that page and tell us the name of the Slider.
Also create a second test page that only has the show post filter inserted in the content area and give us a link to that
Now because you said you created a filter I am assuming you want a post slider. But if you wanted an image slider, then all you would need is to create a slider post with a wordpress gallery of all your images in it, and use that slider post for the “Slider Post Slug” (set to show slider as images).
So you may want to clarify what type of slider you are trying to make.
September 22, 2015 at 03:10 UTC - Views: 2 #24657Qoheleth
ParticipantGot it. For whatever reason, it won’t work injected into the premain area, but it works just fine added to the content area using that very-handy-by-the-way button in the editor. I was sure I tried that earlier, but it’s surely working that way now.
Yes, it is indeed a post slider I am making. It rotates through posts in the category Featured Items. (That makes it very easy to set which posts appear in the slider, adding new ones as they’re posted and dropping earlier ones. I can do the whole process using QuickEdits.)Anyway, thanks for the assistance. The response time on issues is one of the reasons I like weaver.Consider this solved.September 22, 2015 at 05:40 UTC - Views: 3 #24658scrambler
ModeratorThis is not resolved then because it should absolutely work in the premain area.Can you make a test page with the exact same shortcode in a page custom field called premain and in the content area and post the link hereSeptember 23, 2015 at 13:13 UTC - Views: 5 #24659Qoheleth
ParticipantSure. As it turns out, It really isn’t working.
Here’s the odd thing: If I put a Premium Featured Posts Slider [fps] on the page, then the Weaver Slider also appears. If I don’t, it doesn’t. The HTML code I see, using right-click Inpect Element in Chrome, shows a width of 0 when it’s not working and 653 when it is. It looks like something it’s inheriting from somewhere, which is modified by FPS when it shows.Here’s another odd thing: Nothing I insert into premain shows up, including [fps] and, if the [fps] is in premain, the Weaver Slider doesn’t show either, no matter where it’s put. What works is putting [fps] into a replacement top widget. Then the Weaver Slider shows up in the content.Here’s the link you requested:This page works — http://www.disciplesnet.org/test-page/This one doesn’t — http://www.disciplesnet.org/test-page2/September 23, 2015 at 16:55 UTC - Views: 1 #24660scrambler
ModeratorThis is staring to sound like interference with a plugin.
You need to try and deactivate ALL non weaver plugin and see if that fixes the issue. If it does reactivate one by one to find the culprit
September 24, 2015 at 00:06 UTC - Views: 1 #24661Qoheleth
ParticipantNo luck with deactivating other plug-ins. I did discover something interesting in the process: One option on FPS is “ If your theme doesn’t already have jQuery included enable this option. Default: unchecked.” It’s checked. If I uncheck it, the FPS slider shows, but the Weaver Slider doesn’t on test-page. If I check it, they both show.
September 24, 2015 at 00:50 UTC - Views: 1 #24662scrambler
ModeratorWeaver already loads jquery, so you should not enable the option. If the plugin was loading another version of jquery that would be a very good reason for breaking the show slider plugin.But are you sure you deactivated ALL plugins at once, including the FPS to test?Because I see a lot of jQuery errors in the console, which again points to something screwing up jQuery. If something is loading the wrong version of jquery it would explain why the slider is not working. The slider itself is there and all the posts images are in, they are just not being turned on by the script.September 24, 2015 at 08:54 UTC - Views: 1 #24663Qoheleth
ParticipantI just did it all over again to make sure. I disabled everything except Weaver Extreme Plus, Weaver Show Posts and Show Slides. No joy. I’m looking through things with a fine-toothed comb now to see if I have some offending CSS somewhere that’s setting a height to zero.
September 24, 2015 at 17:05 UTC - Views: 2 #24664scrambler
ModeratorNothing is setting the eight to zero.
The way the slider works, is that all slides are laid out with display:none, then a script changes the current one to display:block so it becomes visible. It looks like this is not happening, so the reported height shows zero because no object as set to be displayed.
@weaver, can you help with this one.
He has a weaver show slider inserted in the content area of the page http://www.disciplesnet.org/test-page2/ that is not working. The slider and all the slides are in the page, but no slide is ever set to display (which make me think of a jQuery problem).
If he adds a slider from another plugin with it on the same page here http://www.disciplesnet.org/test-page/ then the weaver slider does work.
He says if he deactivates all plugins it makes no difference, so if it is a script issue , I don’t know what else could be involved.
September 24, 2015 at 21:45 UTC - Views: 2 #24665Qoheleth
ParticipantFound it [long series of exclamation marks]
The offending bit of code was a script in an e-mail subscription widget. When I take out that widget, everything else works.If you’re wanting a look at the code itself, here’s where you can view it:BTW, I appreciate all your efforts to help me track this down, including indicated where I was chasing a false path.The best thing is that I can ditch the Premium FPS now. The second best thing is that I already have an official MailChimp widget that should solve the hacked-together code below:September 24, 2015 at 22:17 UTC - Views: 2 #24666scrambler
ModeratorThe problem in your script is exactly what I was afraid of, it is loading its own version of jQuery in the line
<script type=”text/javascript” src=”http://ajax.googleapis.com/ajax/libs/jquery/1.2.6/jquery.min.js“></script>
Given weaver already loads the proper version of jQuery, you could try just removing that line in your script, and see if the script works with the regular jQuery version loaded by weaver
September 24, 2015 at 22:25 UTC - Views: 1 #24667Weaver
KeymasterWordPress is VERY fussy about loading non-approved versions of jQuery. It will only work reliably with the latest approved version bundled with WordPress. Just too many other dependencies for things to play well together – as you found out.
September 24, 2015 at 23:44 UTC - Views: 1 #24668Qoheleth
ParticipantSure and of course. It’s quite obvious in retrospect. That code was one of the last vestiges of the former web programmer. Thanks for sorting the exact nature of the problem for me.
-
AuthorPosts
- You must be logged in to reply to this topic.

