I had done this for 6.5.x and it was essentially a standalone. ie: just upload and poof, done.

This one is much more integrated, in that it ties into the "My Stuff" menu.

It also takes advantage of the Smarty stuff to allow me to totally remove an rssGenerator class I had to code.

Essentially, clicking on the My Stuff menu, shows an additional option:



Clicking on that option will query the DB and return a list of feeds that the user can subscribe to like so:


Full size

Note: feel free to change the error message and general description stuff.

All the rss icons are feed uri's and can be added to your feedreader of choice. since they are generated per the user's read-rights, there won't be any wrong uri (per se).

But in the event that a user starts playing with the link, they'll get the following error message (configure as you wish in - language file)



I've included the general links as well:

1. PM inbox messages
2. Active topics
3. Active posts

Works outta the box for both 7.1 and 7.2 and fits with the standard structure: scripts, templates, language.

Enjoy!

ps: i added 3 < div id="xxx" > around the major chunks of the html side of the template, so you css'ers can go crazy with some fancy smanchy stuff. for those who don't know or care about it, the divs will be transparent anyway

Nice.

Very nice. I may just have to get this into the stock code for 7.3

thanks Rick. i'll polish off the wish list then and also combine some copy/pasted code/template stuff.

the last push i made to get it done left a couple of chunks of semi-duplicated code.

should be done by tonite.

well hurry up then

Seriously - many thanks

will hop right on it then

Updated readme.txt and .zip file. Bug in header.tpl and in generic.php

I do rather like this for the record

ok, i cleaned up the code. drastically reducing it's size, including the bloated template too.

only thing remaining is to get the PM inbox to work and i'd call it a wrap.

i'll upload tomorrow.

well done Thanks

hrm.. feeds work fine, but i'd really like to add a tweak for those forums that are essentially available to guests as 'read'

i'm going to add that in..

ok, got that.

now just working on making the feed be valid according to w3c. now it is

Excellent work

Hat comes off and thanks you too

Rick Hurry up and put it in b3 not 7.3 lol

All done, PMs in and w3c checked.

Enjoy!

Awesome... Validation = key

hehe, yah, the last validation quirk was that the smilies were relative Urls and not FULL urls. I didn't know w3c would be that picky..

oh well

It wanted full URLs? that's stupid... I have 5 domains for my site, and all have to work independantly; not to mention have to support SSL; so that's 10 domains that would have to work independant... so if a user was blocking (well, if their isp was) my main url, they can usually get in via my ssl, but if it was hardcoded all urls then i'd be sol lol...

giz, that's not the issue.

the url is relative in the description, but when shown and you'd right click on it, you get full url.

it's just that the w3c validator wanted it to be full in the description to start with.

smileys as they are now are relative anyway. %%GRAEMLIN..%% is replaced by a relative URL (style array path) for display. you'd have uber-probs, if that didn't work.

no biggie

just add '$config[FULL_URL]' and poof done.

i ran into this same issue, when i was coding up the 'Email Thread' mod. All smileys puked (at first) in the received Html Email

:snicker: I set $config['FULL_URL'] to $_server['HTTP_HOST'] and replaced "http" with my ssl monitor

m'kay.. whatever fluffs your flannel, i guess

by setting it to http host it reads the domain it's being accessed as; so you can set it to allow posts from any domain (as some portions will set you as the domain set in the forums); and the ssl stuff is a nessessity to bypass some more-stupid site filters

dude, you completed missed my point (or we are just off on some tangent not related) of why it's recommended for full urls in description or in an email and why w3c flagged it.

example: for smileys, the non-full url is '/images/graemlins/default/smile.gif'

that works well and good, if that url is on the site itself, but blows up in an email where it's NOT being read from the site itself.

example (i copied raw html from my initial post in this topic where i have the wink smiley):


assume i email that to myself and then try to read it ... dead smiley link

what you end up in an email is broken links for every smiley and where i didn't notice it in the feed was ok. and the feed will be ok with relative urls, but still not a w3c recommended practice. emails are prime example, where it just plain blows up.

so bottom line is w3c makes sense and the fix was a minor one to be in compliance.

no need for redir or whatever hokus pokus to fix this problem. i just needed to do it right in the first place and thank god for feed validators as well as the other ones.

regardless. back to topic..

true, that would be a dead link if emailed to someone like that...

But i like my hucus pocus

fixed a couple more bugs and added some more features. i will update the readme and add some screenies. now 7.2 compatible and soon to be 7.3 ready.

essentially, it's more integrated into ubbt and has even more functionality..

all in keeping with the 'drop in' philosophy...

film @ 11