[RC1] Full Syndication Suite 1.0.RC1 (RSS/ATOM)

[hurry]

Any news Tuk on the next version? I want a bug fixed version at least with the session id and missing topic_id problem fixed as when people are clicking the rss item links in the email it giving them an error page. Please release the version with these bug fixed so that at least things work properly.

[Tuk]

I'm working on it, there are still two issues I would like to work on before releasing the next version. It shouldn't take that long any more .

Edit: Nearly finished, new version will be published sometime today.

[Tuk]

Say goodbye to "Advanced Syndication MOD", welcome "Full Syndication Suite" .
The MOD has been renamed to give it a more meaningful name to fully pointing out its scale .

New release: Full Syndication Suite 0.9.0a

All initially planned features are now implemented, thus I decided to bump the version number up to 0.9.x. Feature requests are welcomed nevertheless.

Changelog:

• Introduced forum based permission settings for syndication.
• Some optimizations and cleanups here and there.
• Fixed constantly changing session ids (thanks to hurry).
• Custom feed generator no longer generates invalid feed when no options were selected.
• Added license.txt file to package required by MODX.
• Moved functions into own file.
• Added load setting for caching SQL queries.

Changed files:

• generate_feed.php
• create_syndication.php
• includes/functions_syndication.php (new file)
• includes/functions.php
• includes/acp/acp_board.php
• language/en/mode/syndication.php
• language/en/acp/board.php
• language/en/acp/permissions_phpbb.php
• styles/prosilver/template/syndication_rss2.xml
• styles/prosilver/template/syndication_atom.xml

When updating, you should also run sql_install.php to add the f_syndication permission and change existing roles.

[hurry]

I think I did everything correctly for 0.9.0a and modified the files which you have mentioned and ran the sql php page too.

It gives an error now:

[phpBB Debug] PHP Notice: in file /generate_feed.php on line 202: Undefined index: syndication_ttl
[phpBB Debug] PHP Notice: in file /generate_feed.php on line 266: Cannot modify header information - headers already sent by (output started at /includes/functions.php:3264)

You can check yourself. How to solve this? Thanks.

[Tuk]

For updating, you also need to execute

Code: Select all

INSERT INTO phpbb_config (config_name, config_value, is_dynamic) VALUES ('syndication_ttl', 300, 0);

and delete cache/data_global.php afterwards.

[hurry]

Ok I did that, now the errors are gone. But the generated RSS feeds do not show 50 posts in the feeds even though 50 is selected as default. They randomly show 1 or 3 or 10 or random posts in the RSS feeds. You can please check. How to solve this? I think that when the post contains some complicated html like js or something, the feed generation seems to stop at that item and proceed no more. I hope there is a solution.

The good news is that the prosilver template style errors seems to be gone.

Edit: One really cool thing though. The flash video players with object and embed code or js code are now appearing perfectly in the RSS feed both in Feedburner and Feedblitz which is quite great. Thanks. Please solve the above problem though.

Edit: Can't use the RSS feeds at all now as they are showing only a few posts, so please help.

[hurry]

Sorry Tuk for bothering, but just wanted to know if this problem can be reproduced at your end. I am stuck at this point with the RSS feeds not working. I can go back to the your old version to make it at least work for now but I am sure you will fix it. Please do let me know.

[Tuk]

I did see this sometime during development, but wasn't able to reproduce it right now. As far as I remember it was caused by a customs BBCodes's java script or something similar to that. Could you check, which custom BBCodes are involved when this problem appears (or just post the topic id with posts causing this here so that I can check myself)?

[hurry]

It is getting stuck at all bbcodes even the [ url= ][ /url ] ones and I guess maybe the img ones also though I have not tried the img. It gets stuck at the posts with Youtube, Google Video and Videoegg embed codes. But surprisingly for the videos from my hosting which I embedded inline with the normal flash object and embed code and the below one from veoh there i sno problem:

No problem for this veoh code:
<embed src="http://www.veoh.com/seriesplayer_embedded.swf?permalinkId=channelname" width="640" height="480" type="application/x-shockwave-flash" pluginspage="http://www.macromedia.com/go/getflashplayer"></embed>

The following Google Video is a problem:
<embed style="width:400px; height:326px;" id="VideoPlayback" type="application/x-shockwave-flash" src="http://video.google.com/googleplayer.swf?docId=1526183102745208142&hl=en" flashvars=""> </embed>

Youtube code is a problem.

And VideoEgg, the below js code gets stuck:

<script language="javascript" src="http://update.videoegg.com/js/PlayerCustom.js"></script><script language='javascript'>var api = VE_getCustomPlayerAPI('1.0');api.embedPlayer('/gid328/cid1096/SG/IA/2264692604ocHWnjQybFVlQNA8M4iL', 350, 330, false, '', 'videoegg', false, '', '');</script>

But the following VideoEgg flash embed code works:

<embed src="http://static.videoegg.com/videoegg/loader.swf" FlashVars="bgColor=FFFFFF&file=http://download.videoegg.com/gid328/cid1096/SG/IA/2264692604ocHWnjQybFVlQNA8M4iL_high.flv&autoPlay=false&forcePlay=false&logo=&allowFullscreen=true&allowFlash9Fullscreen=true" quality="high" allowScriptAccess="always" bgcolor="#FFFFFF" scale="noscale" wmode="window" width="320" height="260" name="VE_Player" align="middle" type="application/x-shockwave-flash" pluginspage="http://www.macromedia.com/go/getflashplayer"></embed>

[Tuk]

I can't confirm that, none of your mentioned BBCodes break the feed on my test board . Although I see this happening on your board.
Could you try switching to ATOM (setting in UCP) and check if the problem also occurs there? Somehow I don't think this problem is caused by a wrong output. I saw this happening on your board with posts which contained only the [b] BBCode. If you can confirm that the problem also appears with ATOM, I suspect that one of the SQL queries is doing something wrong .