Vanilla 1 is no longer supported or maintained. If you need a copy, you can get it here.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
Feed Publisher
This discussion has been closed.
Comments
The xml declaration was missing for RSS2 feeds, now it's here.
Hey, are you all English talking people? I received no translation yet!!!
EDIT: hope it will be lite enough for you dan39 !!!
Additionally, the manual configuration of category feeds enables someone to create some simple .htaccess RewriteRules to make the displayed URLs for the category feeds pretty. So, the manual configuration currently allows for more flexibility in setting up the category feeds -- which tend to get the most traffic. Also, Vanilla usability tends to work best when there aren't too many categories. So, it shouldn't be that hard to maintain.
But yes, this manual process is left over from CrudeRSS (and that was why it was called "Crude" in the first place). It allowed for more options, but the pain-in-the-ass manual set up was not perfect by any means.
Both of these things could probably be achieved through PHP, but I didn't go down that road since it was so easy to do with an easy manual set up and it allowed for easy monetization.
EDIT: If it does ever get automated, it would be nice to keep the categories_config.php file there as an option that can be activated in case someone wants to do FeedBurner and pretty-URLs and such. So, by default, the process would be automated. But, it could still be customized in a manual way if someone wanted to. That would be ideal.
You also make a good point in the meantime. Every time a new release is seeded, it's a pain to have to re-copy the categories_config.php file and check for new changes. I think it will make things smoother if the upgrade instructions are phrased a bit like WordPress's and Vanilla's upgrade instructions. For instance, on WordPress, they always tell you to keep your old config.php intact and overwrite everything else. I'm pretty sure that Vanilla is the same way with the /conf folder.
The same kind of basic upgrade instructions would be helpful for Feed Publisher.
----
@grahack, I'm sure the lightness of it will be fine...!
Gonna install this one and have a look...
Mark explained me some usefull things about the framework and grabbing some code from other extensions, but I think that FP is not ready for that.
If you want something working right now (or about), you could copy-paste some code of FP "here" and "there". You could easily mimic FP's behaviour. Just keep the "include" to catch my functions in functions.php (publishing) and global_functions.php (browsing) in FeedPublisher's dir and not the one of FeedPublisherForBlog.
If you plan to work on this, please register on Assembla so we can follow the dev of the beast.
- delay thing
I don't understand your question, sorry, please retry!
- number of feeds
I'm not sure to understand this one too
do you want to save some server load? I don't clearly understand the goal
nice idea, but why the 10 last items? do you mean 10 items in one minute?
see here
@klod: ok, I understand now,
"DELAY" -> you want a cache engine on Feed Publisher, why not... I never built one, somebody has tips, tricks, docs ?
"NUMBER of FEEDS" -> I still don't understand the reason for this (please explain what for), but you could try to tweak the
default.php file until I understand what you want.
Here are two lines where you could insert a condition (in the while loop) to limit the number of feeds. The hack is dirty but maybe will do what you want.
EDIT: added in the while loop
$Context->Configuration[ 'AUTHENTICATE_USER_FOR_FEED_PUBLISHER' ] = 1;
by
$Context->Configuration[ 'AUTHENTICATE_USER_FOR_FEED_PUBLISHER' ] = 0;
in the default.php.
I plan to implement this as an option in the next release of FP.