Serendipity Forums

The RSS Aggregator plugin has an option which allows an aggregated entry to be updated if the original has been updated. On the site I have aggregated the entries TO, I have extended property fields. I aggregate an entry then edit the aggregated entry to supply values for these extended property fields. If the original entry is updated, I lose the values for my extended property fields. This is not what I would expect - I would fully expect the entry body to be modified (ie, had I changed the aggregated entry, I would expect those changes to be lost by the update). I do not understand why my extended property fields, which are in a different table (not the entry table), are lost on update. Is this behavior necessary, or could the value of those extended property fields be perserved even if the entry is updated?

Hi!

The aggregator updates an entry with all the data from the feed, and thus deletes any custom data, that is true. The concept of the plugin is to work from the original RSS feed source, it is not really developed to take local changes into aspect.

Of course, the plugins' concept/coding can be changed to go your way, but this would mean quite some additions to the code, it's not a matter of removing a "delete all old" checks. In fact, the save logic will have to first fetch all entryproperties, merge them into the $serendipity['POST'] array, then call the updertEntry Routine etc.

Even though I understand your personal need, I'm not sure this is something that a lot of people would use. Usually, aggregated entries are not meant to be locally edited...

Best regards,
Garvin

Seems to me that extended property fields, which are not part of the original feeds, should be unaltered. I would personally only expect changes to what is actually contained in the feed to change.

Now, that being said, what I would REALLY love to see is a way to bring more in to an entry when the source is known to be another s9y site.... and perhaps, the aggregator plugin is not the place to do it... not sure.

What I really could use is a way to use a single s9y site to populate other s9y sites. Think of it like a syndicator, instead of an aggregator. I write an entry on one site, and through choices made either on the origination site, or the destination site, that entry is copied/fed/sent/received by/to another site. I would like to keep entry body and extended body in tact as originally written. I would also like to keep extended property fields in tact. I'm less concerned about author names and categories, but I can see value in that as well. Perhaps some way to choose what to keep, and what to override would be cool.... as would the ability to map one extended property field to another.

I know, I know - this is not normal blog useage, is near impossible, and everyone's busy......