Here is the scenario of what I am encoutering:

I have a user on my website. He/she has permission to create a new feed but is NOT able to use "advanced feedapi options" permissions so the only thing they can do is add a URL. When that person adds a feed, the feedapi settings (e.g. Refresh feed on creation, Pause automatic feed update, etc.) are not being saved. I know this because when I view the settings column in the feedapi table, the value is 'a:0:{}'. However, if the user is able to use "advanced feedapi options" permissions, the settings are saved as I can see them in the database. So, my question is, why are the 'content type' settings for 'feed' not inputted (or inherited from the content type settings) into the database when a user does not have "advanced feedapi options" permissions?

I did quite a bit of searching on this issue and either this problem is called something else or I am not on the right track. I can't be the first person to encouter an issue like this. Additionally, I tested this issue on a clean install of just Drupal 6.11 and FeedAPI 6.x-1.6 followed by running the automated tests. If you need more info, please let me know. Thank you for your time and an awesome module!

Comments

alex_b’s picture

alex_b commented
Version: 6.x-1.6 » 6.x-1.x-dev
Status: Active » Closed (works as designed)

This is by design: if a per node setting is not present (as in the case you describe) FeedAPI falls back to the node type settings.

FeedAPI always stores per node feed settings if the user has the 'advanced feedapi options' permissions.

Do you encounter any problems with this behavior?

mkinnan’s picture

mkinnan commented

I see and that makes sense. However, I do have problems. For example, I have a user without 'advanced feedapi options' add a feed. Now, in the 'content type' settings for feed I have the box checked to 'Pause automatic feed updates' so that when a user adds a feed it doesn't start updating. However, since there are no settings for the feed stored in the database, the feed starts updating even though by default it should not.

This is an issue because if the feed inherited the default settings it could, for example, give an admin the ability to 'map' the feed, check the feed, etc. before it would start updating on the website.

mkinnan’s picture

mkinnan commented

For anyone else experiencing this same problem, you could use rules (http://drupal.org/project/rules) to run some PHP code and update the database when a new feed is saved. Therefore, the settings such as 'Never Refresh' would be injected into the database upon saving a need feed.