I have a client that is using the ExpressionEngine CMS. Up until recently, they had one blog with an RSS feed. They then created a second blog, with its own RSS feed. They now want to move some of the older posts in the original blog over to the second blog, as they fit better in the second blog.
My question is this: if we just re-categorize the blog posts, are these older posts going to show up in the second blog's RSS feed, and if they do, will they appear as new posts?
There are three main reasons why older posts may show up as new in a feed reader:
The GUID or permalink to the post has changed from what it was before
The post was not previously in the RSS, regardless of its date
The pubDate has changed indicating a new item compared to the existing cache
Most aggregators look at the GUID or permalink first to determine uniqueness of item and whether or not to have it show up as new. If neither of those are present they may fall back to the pubDate element.
Just changing the text or category of the post usually doesn't send out a signal that the post is new.
Unless of course changing the category also means it turns up in another RSS feed, as in your case, in which case, it will show up as new no matter when you posted it.
Related
I purchased a plugin that allows buddypress users to add new pages to their profile and ran into an issue that caused me to reach out to the developers, only to realize that this seems to be an issue with every custom post type, and is not isolated to a single plugin. This very well may be a Wordpress thing, but this is extremely inconvenient and I was wondering if there was a way around this.
When users add new pages to their profile, even if the permalink is unique, on the chance that a user names their page the same name as another user, a number denoting a duplicate is added to the permalink.
For example:
User 1 makes a page titled Services (mysite.com/user1/services
User 2 also makes a page titled Services (mysite.com/user2/services-2)
I have changed the post type permalink to include /%author%/%post-name% which works correctly, and changes the permalink, except a number is still added to the end if more than one page has the same title. How can I stop this from happening if the pages are made by different authors?
This was the message I sent to the developers of the plugin, who informed me the issue isn’t really the permalinks, it’s more that the pages are a custom post type and thus beholden to the same slug rules that normal pages have, where if you created 2 pages named “contact”, the second one gets “contact-2” and so on.
I had assumed the user’s buddypress/author page would count as a parent page, but it seems that’s not the case. This appears to occur on my own custom post types as well as any custom post type plugin I happen to use, but I had never tested that until just now. Even if the permalink itself is unique, custom post types cannot have the same title/slug even if created by different users and I can see this hindering user experience.
Does anyone have any thoughts?
Adding author to permalink does not make the page unique. Pages are defined as individual objects and their permalinks are related only to the last section of the link.
The system compares only the post name (the slug) not the full URL or permalink.
mysite.com/user1/{post_slug}
If the {post_slug} is the same as another post slug then the system adds incrementation.
Just to clarify the answer - The post permalink is defined by the post slug and not the permalink itself.
What I would do in your case is to set these pages to an ID-based permalink.
This seems like a simple question but can't find an answer anywhere online.
I have a Wordpress site that, whenever a post gets published, pushes an email out to feedburner subscribers. Very straight forward.
My question is, I need to change some of the posts to privately published so I can test some new stuff and I dont want subscribers to get an email to an empty post.
Can someone lead me to somewhere where it explains what gets pushed and what isnt?
I'm assuming it wont but want to confirm.
I need to change some of the posts to privately published
If that results in the posts not being in the original public
wordpress feed, then there's no way for feedburner to get them.
So view the wordpress feed in a browser window where you are
not logged in to your wordpress account.
However, if you've set your Wordpress feed to have eg.
the 50 latest posts (the maximum), and a post that you make private
is within the those 50 , don't be surprised when Wordpress then provides
the 51st post to Feedburner, which may get re-emailed.
I've been using the RSS feed of my personal site to export its posts to a Wordpress installation, using the plugin FeedWordPress.
In its current state, when a post is deleted from my personal site, it also disappears from the RSS feed, but remains on the Wordpress installation (an undesirable behavior). There is an option in the FeedWordPress plugin to retain only the posts that are currently in the RSS, but then I have a different problem, because only the latest 50 entries are stored in the RSS at any time, so older posts would be deleted as well.
The most promising lead for a solution came from another option for the plugin, which goes:
Allow Feeds to Delete Posts: Yes. If a feed indicates that one of its
posts has been deleted, delete the local copy syndicated to this
website.
How would I go about adding such a deletion indication/signal in my RSS feed?
I would use the built in option in feedpress or create a category and add the unwanted posts there and exclude them from the feed.
Turns out it was referring to tombstones (deleted-entry elements) in Atom.
https://www.rfc-editor.org/rfc/rfc6721
I'm working on a latest version of wp.
I need this kind of functionality but not sure how to do it.
I want to post an blog article which will be available on its main category listing page for set period (from published from & to date - to date is the last date until when it will accessible on category page using pagination. But after to date this will not be list in category using pagination. But still stays on given url and accessible by direct url for SEO reason.
Basically I want to make a pagination to be valid for only a post published under certain period.
Both cases are fine, do you know any plugin which can be used or need to customize?
I don't know about a plugin, but you can simply customize your wp_query: http://codex.wordpress.org/Class_Reference/WP_Query#Time_Parameters, and make sure you use the "paged" parameter described here: http://codex.wordpress.org/Class_Reference/WP_Query#Pagination_Parameters
Can a post be hidden from home page, archive view, category lists etc. and viewable only if you have a direct link to it? The blog doesn't have registered readers and is open to public so that would be a mean of hiding some posts from public view without using the password protection.
I asked this question in Wordpress section and the idea there was to use conditional code so I'm asking the question here as well to get closer to the code.
If I used conditioning, would I have to input each post's ID separately to PHP file for archive, categories, search and such?
EDIT:
After reading a bit more all over, I had an idea of creating a private category and then use some kind of conditioning so that posts from that category are hidden. According to Codex, certain category can be hidden from, for example front page but I don't know if there's a way to hide it altogether except when you have a direct link.
Creating a "Private" category is a good solution. It is quite possible to hide this category altogether except via direct link. You just have to "block all the exits" with conditional code.
The default WordPress theme displays posts via the Post Loop. See http://codex.wordpress.org/The_Loop, especially the section entitled "Exclude Posts from Some Category". Just find all the places in your theme's PHP files (e.g. index.php) where this loop is used, and add the conditional code. You'd also need to filter your category list and blog archives in the side menu. Don't add filtering in single.php, otherwise the private post won't display on its own page.
You'd probably want to add a similar condition to filter search results so that private posts aren't leaked via the blog's search tool. There may be more "exits" I haven't thought of, but I'll be sure to update as I do. I'm glad to look at specific code if you so desire.
Understanding WordPress' post query and loop really opens up a world of possibilities for customization.
I found the simplest way - just use Simply Exclude Wordpress plugin. It has the option to exclude each post (or tag, for that matter) from front page, archive, search or feed. It works flawlessly. You can still view the posts by using direct links.
(Not actually an answer that includes code but a working solution nonetheless.)