This content has been modified by another user, changes cannot be saved

I have the same problem. I comes from the node_validate call on line ~1569 in aggregator.module

See node_validate checks for a couple of things. one of them is

 if (isset($node->nid) && (node_last_changed($node->nid) > $_POST['edit']['changed'])) {
    form_set_error('changed', t('This content has been modified by another user, changes cannot be saved.'));
  }

line 1537 of node.module

I found a tweak that works but i think there must be another way to do it.. anyhow that's what i did:

in aggregator2.module, i added
$_POST['edit']['changed'] = time(); before the call for node_validate. for some reason the error started showing up soon after. So i did the following:

	$_POST['edit']['changed'] = time() + 1000;
	node_validate($feed);
	$_POST['edit']['changed'] = time();

It's working for now, but dunno if it's the best solution..

now it seems in the latest cvs version the node_validate call was removed... Try updating

Oops it seems the CVS update has been made to the 4.6 branch. What they did is just add a
$feed->validated = TRUE; instead of the node_validate call.. But it's not the best solution..

I have this same error too... hmm.

same problem here as well...

Please post a patch as described here: http://drupal.org/diffandpatch

Here's a patch. It's supposed to work fine. I tried it and it's working but it needs some testing...

Here's a patch. It's supposed to work fine. I tried it and it's working but it needs some testing...

the patch idea was ok but I think it was missplaced. I first tried the previous patch uploaded by ziz but this error keep happeninig. I guess this was a validation added on the newest drupal core, because I recall this not happening on the previous versions.

Anyway, I attach the patch against the lastest -cvs.tar.gz package of the module (v1.43 cvs version of this file). Hope this helps.

a.=

Ok.. what I talk about previously was wrong.. the fix was correctly placed, althouth that was for fixing the validation for the feed node type. I aslo found that the feed_item node types were failing too, so I added that same workaround on another place of the file.

I also found another error, which I might post on another issue, thus when the module tries to update an already stored item, it loads the taxonomy information twice, and because of t his warnings of duplicte keys on the taxonomy table appear on the administration page.

I found why this was happening. It is documented on the code that node_load() does not load the taxonomy information, so the module loads it itself, but node_load does include that information.

The patch I am attaching has the previous workaround for the validation error and also this error fixed.

Hope this helps, the patch was made agains the same aggregator2.module file I mention on my previous post.
a.=

Hanoii, for the duplicate entries bug, there's a patch that's working and ready to be comitted: http://drupal.org/node/81085

it's great to have the patches of aggregator2, but I believe the new version (leech_news) will replace it.

I got email from the assigned developer ("ahwayakchih") of aggregator2 and the author or leech_news and he is coming back Sept 18!! Just want a little over a week for development to begin again and the bugs to get worked out in a brand new version of leech_news...

Hi, just applied the patch (aggregator2.module_4.patch) and it seems to work OK for me.

Small point - it looks like the patch is a reverse patch? Is this intentional? (It might be the norm for drupal patches but my very brief skim of the documentation suggests not ... ;-)

Cheers,

David.

Would it be possible to attach the patched module here, so I could download it as well?

Thank you!

Mario

Actually, could someone please post this module with this patch and the patch that will allow categorization of feeds. I was able to apply the categorization of feeds patch http://drupal.org/node/61474 but I couldn't get this patch to work after I applied that patch.