Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ability to edit post types. #18

Open
thejourneyler opened this issue May 4, 2012 · 2 comments
Open

ability to edit post types. #18

thejourneyler opened this issue May 4, 2012 · 2 comments

Comments

@thejourneyler
Copy link

I am running a timeline with 70+ events in it.

Each event is grabbing my jetpack Share options. That means that for each item on the timeline the plugin is treating it as a separate post. So on each page hit WP is trying to query 70+ posts. (my understanding anyway) I use a cashing plugin, so this helps some on the load time, but it still takes time. I am wondering if there might be some why to turn off the "Share this post" option on just the posts in the time line. How might this work? am I missing something?

http://wordpress.org/extend/plugins/wp-facebook-timeline-mf-timeline/

Wanna see the time line in real live?: http://hugh.thejourneyler.org/2012/timeline

@matt-d-rat
Copy link
Owner

The timeline plugin pulls in the post excerpt for each post on your wordpress blog using the apply_filter('the_content') function provided by the Wordpress API. If the 'jetpack Share options' is hooking this filter, which I can only assume it is then this is most likely why it is appending the share options to each post - which is the correct behaviour in terms of the functionality provided by this plugin.

I agree that this is obviously quite slow and taxing in generating the page request, but there isn't anything I can do to prevent this plugin from hooking the post content at this point.

I will be adding AJAX loading to the plugin soon so that not all content is added in one go - which is currently what happens, I just haven't had the time to develop it yet. Hopefully this will resolve your issue when I have had a chance to implement the changes.

@thejourneyler
Copy link
Author

Thanks, Well, I'll update when you release your AJAX update.

Actually, after some more thought, perhaps if the plugin could be coded to use a custom post type, rather than a standard post type then would the filter apply_filter('the_content') still apply? Perhaps what would be useful would be if the user can select if they want to use standard posts or if they want to use custom posts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants