Wooliet

Try this:

$container.data('masonry')['_reLayout']()

I just updated my WP install to 3.5 the other day and haven’t noticed any issues. I have no idea how headway themes work or if that has any bearing on the issue.

If you end-up trying it out again, and still have issues, post a link to your site and maybe we can figure it out.

Try binding the context of the call to your new element using jQuery’s “proxy” method. Something like:

$.proxy($ fn.ReadMoreRightHere, $('div.dynamic-content')[0])()

I really don’t know about shortcodes. I remember when I wrote the plugin I tried to make sure that whatever content was grabbed, it was sent through the normal wordpress mechanisms. There must be something extra to have it run through the shortcode process. I don’t know when I’ll ever have a chance to look at this again. If it’s something you’re comfortable with, feel free to insert new code after line number 679 in “read-more-right-here.php” that calls the WP method for parsing shortcodes.

As far as the re-executing the javascript, that comes up from time to time and there’s no real good answer. If the client code executes once when the page is ready (e.g. jQuery’s .ready), there’s no way to know what needs to be executed again. See the second and third items in the plugin FAQ for possible solutions.

You can try running masonry on your content when the plugin ‘expanded’ and ‘collapsed’ events are triggered. Check out the third item in the plugin FAQ, “Is there anyway to determine when new content has been displayed for a post?“.

wpwlearner, can you post a link to your site, or some more info regarding this issue? I don’t quite understand.

Also, I released a new version a couple of days ago. When you have a chance see if it happens to resolve your problem.

Does the problem seem to be limited to Opera?

—

I just installed Opera and it’s working fine on my site. What’s your URL?

There really is no simple solution right now. The explanation is that most plugins wait until the web page is loaded (to ensure all required elements are there) and then perform some action on those elements.

When RMRH pulls in new content, it’s too late. The other plugins don’t know its there and nothing will happen.

What has to happen is that the javascript of the other plugins (or ads or whatever) needs to start monitoring for the creation of new elements that match the type on which they act. In other words, instead of

Wait for the page to load, find all images, and do this to them

the code needs to say

Every time a new image element is created, do this to it

jQuery has live and delegate to accomplish this.

No idea. Those are function names and the error line is at the closing bracket for each of them, which is also the last line of code before they are added as an action and filter.

So it’s like the functions definitions are missing, and so when referenced in calls to add_action and add_filter, PHP thinks they must be constants.

But again, no idea why that would be.

I would setup a rule for read less links (a.rmrh-show-less) that hides the link text and sets your image as the background-image.

You can hide the text using something like this method described at stackoverflow.

Can you post the URL to the site?

(link to other thread for future reference)

poosk: Does any of the above help you? If you’ve got a template setup for display posts within that particular category, then I would think that what is described above might be useful in solving your issue.

I had to look up “Yatta”. I like that word.

Glad you got it working! I guess the goal here is to add something so that that the plugin is only activated within a particular template.

Here’s what I’m thinking. I can’t test anything right now so please let me know if I’m way off here, but:

1. You can remove the ‘more link’ filter using remove_filter (reference) within your other theme files. E.g.:

remove_filter('the_content_more_link', wt_rmrh_morelink_filter);

2. Within the template where you do want the plugin to work, just add the global $more;$more = 0; code before your call to the_content. (And obviously done’t call remove_filter)

This way you’re not messing with the actual plugin code. Does that make sense? Would that work?

I think you would have to modify the theme’s style sheet to target the loader gif.

Maybe something like this at the bottom:

a.more-link+img{border:none}

Let me know if this helps at all.