Will White

Ended up figuring this one out.

Operator error, not programming error.

Just realized that it only works on albums.

Is there a way to do this without creating a sub-page manually for each gallery?

This helped me fix the same issue on a site I’m working on as well.

Perfect timing for this post – thank you for the help!

The problem was with the Interactive Buttons – Facebook/Twitter/Stumble.

Since I could not resolve the issue I was forced to revert to the share icons instead – and those are working fine (which I believe is what you just saw).

I don’t currently have a test page with the interactive buttons loaded.

I discovered that deactivating and reactivating the plugin seemed to resolve the “Saving” issue I was having.

Then I resolved the blank form issue – the upgrade cleared “Attached Fields” under “Form Settings” so I had to re-attach each field.

Things seem to be back up and running.

Update: The issue seems to be appearing in Firefox on both Mac and PC.

Version: 3.6.13

Update: This issue also seems to mainly appear in firefox – Safari and IE seem to handle the plugin ok.

Update: This bug only seems to appear to people who are already logged in to Facebook. A non-logged in user sees the appropriate log-in fields and, after submitting, the pop-up hides and the like button updates without any new pop-ups being created.

The Code I used – now I can use any jQuery etc I want to cycle the entire content div’s – and each div is still editable via separate pages in the dashboard for client use.

[Code moderated as per the Forum Rules. Please use the pastebin]

Just figured it out.

Ended up calling query post to get the specific page, then running the loop, then later on resetting query post to pull the next specific page, then running the loop again, etc.

Thanks!

Grr I started messing with query_posts and I’m having difficulty getting it to pull the contents of pages so I can display them in three separate <li>‘s.

Can you point me more specifically to where I should be looking in this article?

Thats the direction I needed.

Thanks!

Found it. All the html for the forms was in the Language files.

Unfortunately that didn’t do the trick.

After digging for a while I feel like it might be a problem caused by including both jQuery and prototype.js frameworks. What do you think?

Update: I’ve realized its only Internet Explorer 8 experiencing this issue.

IE7 works fine.