Bio not provided
I'll test again after I install your updated version with the filters. Thanks.
2 years, 4 months ago on Tabber
@nphaskins No, that's not cool. Your Viewer plugin does not work and other shortcodes like the HTML5 audio player do not work. Besides, having to manually format pages kind of defeats the purpose of the ease of use of Tabber. I can use tabber to avoid having to manually code tabs, but end up having to manually code everything else and forgo the use of other plugins on the pages being tabbed.
There is something about how Tabber pulls in data from others pages and strips the content when a shortcode is used. Maybe it's the order. It seems like WordPress is not given a chance to process the page being called. I use another plugin that pulls content from others posts and pages and does not strip out other shortcodes. It is called RPS Include Content (http://wordpress.org/extend/plugins/rps-include-content/). Maybe you can take a look at how it pulls in content and use the same method.
@nphaskins Yes, I had renamed the IDs within the accordion, but to no avail. Yes, I was using the accordion shortcodes because it involves less typing, but since you asked, I switched out the shortcodes with standard markup and the accordions now work, BUT the formatting of the text is lost. The content within the accordion sections is rendered as wrapped plain text.
Compare the two pages:
See Songs tab in tabbed page:
@nphaskins I edited the data parent att to be the same as the ID that the accordion was using, but that did not help. But the accordion was working fine before on the singular page when the IDs were different. It's only when it is within the tabber page that it does not work.
And yes, I enabled the Viewer plugin and noticed that it does not work either. Something is amiss, but when you get it figured out, having the plugin and shortcodes working in harmony will allow for a really nice user experience. It allows for a lot of information in a minmal amount of space and no page reloads.
This is a Section like many other Sections in Pagelines. You activate via the Pagelines Store. I have it installed and it is working for the most part, except there appears to be a conflict with the Accordion shortcode which works on the individual pages, but not when they are integrated with the tabber section.
Here is the tabber page:
Here is the Songs page by itself so you can see how it should behave:
@nphaskins I discovered the conflict. It was with the "Better Internal Link Search" plugin (http://wordpress.org/extend/plugins/better-internal-link-search/) which I think I installed between your shortcode plugins which made me think that BA shortcodes was working when this one was not, but turned out neither one was working while the search plugin was installed. Removed it, now your generator plugins work.
2 years, 4 months ago on PageLines Shortcode Generator
@nphaskins @graynotgrey I have the plugin working, but I am getting an annoying error message in the upper left corner on the home page of my web site (no where else on the site), white text in a black box that says the following:
Init failed: Galleria could not find the element "#viewer".
This is a result of debug being enabled in the galleria-1.2.8.min.js. The above error message is near the bottom of the JS file. I tried disabling debug, but could not, so I just zeroed out the dimensions of the fatal message so it does not show up.
2 years, 4 months ago on Viewer
[I tried to email you but I got a permanent failure when sending to email@example.com. ]
Uncaught TypeError: Cannot call method 'indexOf' of undefined post.php:3583
(anonymous function) post.php:3583
(anonymous function) generator.js:7
I have not gone through the exercise of disabling my other plugins yet because there are none I do not want to do without. I'm hoping the error message above provides you with insight on what te problem may be. I had your Bad Ass Shortcodes plugin as well before Twitter Bootstrap was added to Pagelines. I disabled it because I just want the bootstrap shortcodes. BA did not generated the above error. I running the latest version of Chrome on the latest version of OS X. The site is hosted on WPEngine and running the latest version of Pagelines Framework.