Forum Replies Created
-
AuthorPosts
-
After upgrading to Windows 10 it is now working in Edge. I’m not sure what was going on before.
Here you go.
I’m running IE 11. Looking at it through the developer tools in IE 10 it also has the problem. Renders correctly in IE 8 and 9.
Brock
Where it should be (and where it renders in Chrome, Firefox, iOS Safari):
Where it renders in IE only:
Thanks,
BrockThanks! It worked!
It does work for the Color Section though.
Same problem here. :(
October 21, 2014 at 2:35 pm in reply to: header information warning after update to Enfold 3.0 #339009After the latest update release everything seems to be working now. Not sure what it was, but glad it’s fixed.
Thanks!
BrockOctober 20, 2014 at 2:35 pm in reply to: header information warning after update to Enfold 3.0 #338336Hi Andy,
No, I had the Relevanssi plugin deactivated. The problem only exists when it is activated.
Brock
Ok, thank you, Josue!
October 11, 2014 at 5:08 pm in reply to: header information warning after update to Enfold 3.0 #334345This reply has been marked as private.October 9, 2014 at 5:25 pm in reply to: header information warning after update to Enfold 3.0 #333360In order to use this code I still need to have the Relevanssi plugin installed and activated.
I tried it and am still having the same problem.
Any ideas on what to do?
October 9, 2014 at 4:06 pm in reply to: header information warning after update to Enfold 3.0 #333303I have not, so thank you! Before I add that code I just want to check: I put that into the functions.php file, correct?
Thanks,
BrockOctober 8, 2014 at 3:01 am in reply to: header information warning after update to Enfold 3.0 #332044Tried it and I still got the same error message.
Apparently the culprit is the Relevanssi plugin. When this is deactivated, it works.
Any ideas on how to fix this? Because that is a really great plugin.
October 7, 2014 at 12:29 am in reply to: header information warning after update to Enfold 3.0 #331234Seems to be a problem only on pages that include a LayerSlider element.
Hi Ismael,
Well, I guess I need to read the update logs a little closer. :) Sorry about that.
I’ve implemented everything you posted on the other topic and it’s working beautifully. Thank you!
God bless,
BrockThanks, Yigit. That will work.
I sort of figured out a workaround with the plugin Advanced Custom Fields. I created a custom field for the posts and within the functions for the plugin I use to create these posts (it’s a wiki) I set the get_posts array to grab the custom field.
Thanks for your help!
BrockOk, thank you.
There may be another solution to my problem. The issue comes from the fact that I want posts to have a permanent order on certain pages, but I also need those posts to be ordered by “post date” within magazine elements.
If I use the “order” field within WordPress to order the posts permanently on certain pages, then the magazine elements will take the order “0” posts before the order “1” posts, which are taken before the order “2” posts.
Could you point to the code that determines the magazine element order, and is it possible to code it to ignore the “order” field and only order by “post date”?
If I didn’t explain this correctly let me know and I’ll try again. :)
Thanks,
BrockHi Sophie,
I had wanted to do exactly what you posted and eventually found this plugin to create categories and tags for pages:
http://wordpress.org/plugins/post-tags-and-categories-for-pages/
This allows you to use pages in portfolio elements. Hope it helps!
Blessings,
BrockAlso, any thoughts on why it is not interfering with the slideUp but is interfering with the slideDown?
Ok, I figured it out. The W3 Total Cache plugin is interfering. I’m guessing it has to do with the Minify feature. I’ll try to see if I can exclude the toggle function in the Minify settings when I find the time. If you guys already know how to do this and can quickly tell me, I’d appreciate the help and time-saving.
Thanks,
BrockYeah, I did all of that and even just tried it again. Still no luck. It seems to be opening as if there was no slideDown speed designated at all. Each accordion toggle opens immediately without any effect or delay. It operates slideUp just fine, but not the slideDown.
Any ideas on what might be going wrong?
Hi Dude,
Sorry it took me so long to get back about this. Tried your suggestion and it didn’t seem to change anything.
Any other ideas?
Thanks,
BrockThanks, Devin. Yeah, we’re going to concede and just stick with the basic bbPress forum setup. The tab issue still exists on other pages where the tabs display on the left, so if you have any suggestions on what to try next we’d appreciate it.
Also, still looking for help on the accordion and toggle open speed issue. Do you know where I can change it?
Thanks,
BrockHi Ismael,
Super cache obviously works great, as do the other suggestions, but I’m still having the same issues, even on pages with no images. Any specific plugins that might be affecting it all?
Thanks,
BrockHaha, I’ll let you know how it works. Will that also solve the toggle speed issue?
Thanks, Ismael!
Thanks, Ismael! That worked great for separating the two groups. However, the first in the Commentary group (Genesis: http://www.onlinebiblecommentary.com/bible/genesis/ ) still shows the second (Exodus) on both the left and right sides. The same goes for the last in the Bible Bios group (Titus: http://www.onlinebiblecommentary.com/bible/bible-bios-titus/ ) showing the next to last Bio (Timothy) on both sides.
I assume this happens because Genesis and Titus are technically the first and last posts, but is there any way to prevent it from showing on both sides?
Thanks again. You guys are awesome.
UCThanks again! You guys rock!
-
AuthorPosts