garvinhicking wrote:
Sadly I currently have no pgsql installation available to test it with. But maybe it's related to not finding/setting the autoincrement keys automatically through pgsql sequences?
Hi Garv,
My webhosts's Postgres is 7.3.4 so I don't know if this is a bug-free version or not. I only take what they give me.
Anyway, a couple other issues with the Aggregator--I have to say that the output is somewhat "aesthetically challenged" but I could be wrong. Let me explain.
By using the patched tpl, even the original blog entries have that little "ORIGINAL" link appended to it and it basically links back to the blog's home page. Also, the articles that are imported only have a few sentences in them and are cut in mid sentence. So here are my questions:
1. Is it possible to configure the entries.tpl so that it recognizes original blog entries from RSS entries? This is so that original entries do not get the "ORIGINAL" link appended to it, while RSS entries do. Also, it would be nice to append three periods (...) to the end of the last word of the RSS entry so that even if it's cut in mid sentence, it gets a semblance of logic with the three periods. In fact it would be nicer if the "ORIGINAL" link is appended after the three periods. One could change the ORIGINAL to something like "Read full article here" or something like that.
2. If the answer to #1 is yes, are there variables that differentiate between blog entries from RSS entries, eg, {$entry.properties.ep_aggregator_feedname} etc. If there is a previous thread that has already dealt with this, please point me in that direction.
Thanks again!
