Closed (fixed)
Project:
Feeds
Version:
8.x-3.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
15 Apr 2019 at 07:06 UTC
Updated:
18 Apr 2019 at 09:24 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
megachrizAt first glance, when looking at the overview image, it seems that the last one only have the operation "Bearbeiten" (Edit) could be caused by having limited permission for this feed.
When an import starts, Feeds locks the feed being imported as to prevent to start another import while one is running. When an import crashes, the feed remains in the locked state. Feeds then doesn't know it has crashed and assumes it is still in progress. To (re)start an import for such feed, you need to unlock it first. An user needs to have the permission to unlock a feed.
As for the internal server error, that could be caused by several things. It could relate to a bug in Feeds, but it could also be caused by a bug in other module. A configuration error on the server is also a possible cause.
Comment #3
rainer f. gottlieb commentedHi,
thx for the answer.
I have administrator rights but cannot unlock the feed. How can i do this? Please tell me where to find the option for it. Thx.
The internal server error has not appeared again.
Comment #4
megachrizGo to the feed page (for example "/feed/1"). There should be an action link called "Unlock" there. If you can't find it there, can you share a screenshot of the feed page you are facing?
Comment #5
rainer f. gottlieb commentedI have gone to the feed page but no unlock action.
I attached a Screenshot from the feed page. I looked into the permissions and the adminstrator role has the rights to unlock the specific feed types.
Comment #6
megachrizAccording to the last import time on the screenshot, I'm assuming imports for it work normally and the feed is not in a locked state currently. Just the action links are missing.
To be sure, check on the block layout settings page if the "Primary admin actions" block is there in the region "Content". If it is there, check if any visibility constraints apply.
If you haven't done so yet, flush/rebuild caches.
Comment #7
rainer f. gottlieb commentedThanks,
that was the missing part.
Comment #8
rainer f. gottlieb commented