Hi @woober,
The 2.2.0 version is the new version. One reason for this error is a version conflict and sometimes this happens when you’re using a cache plugin or when the browser cache keeps using an older javascript file.
Could you try to clear your cache from the browser and if you have one, from your cache plugin?
Thread Starter
woober
(@woober)
You are right – i should have written v. 1.9.8
I did a ctrl+shift+r to ignore cache. This fixed it, but gave another problem, which also happened in the early versions for me:
It writes this:
This feed has been added to the feed queue and will be processed when it is next.
and when i go back to the feedlist, it writes this forever:
In processing queue
Any thoughts?
Yes, you can try to clear the feed queue by opening the Feed Manager -> Settings page and there press the “Clear feed process” button.
Thread Starter
woober
(@woober)
That didnt do anything. Still writes “In processing queue”.
SOLVED:
Its working now, when i check “Disable background processing”.
-
This reply was modified 7 years, 8 months ago by
woober.
I would advise to try out version 2.2.0 again.
The background processing has some important advantages over the non-background mode. Please try to install the 2.2.0 version again, clear the queue before trying to generate a feed and then generate the feed again.
The 2.2.0 version has an improved background mode so it might work and then you have the advantages of working in the background mode.
If it still does not work, open a ticket in our ticket system (https://www.wpmarketingrobot.com/support/) and tell me if the feed that gets stuck has any products in it or just the xml header.
You can always switch the “Disable background processing” on again of it still does not work.
Hi @woober,
Where you able to give the 2.2.1 version a try?
Thread Starter
woober
(@woober)
Hi
It still doesnt work with background processing. Which doesnt matter, since im perfectly fine with just disabling this feature. So everything seems to be going just as good as v. 2.2.0
OK, but be aware that the next version (2.3.0) will have again a few improvements on these issues, so keep trying out new versions as they come out.
I’ll close your ticket for now then. Don’t hesitate to reopen it when you have any related question.
