• Resolved haychart

    (@haychart)


    feedmanager Version 1.8.1
    woocommerce Version 3.3.3

    stuck In processing queue
    I have done all the pre-requisites
    includes to 512, nothing appears ion the consile and no debug.log
    done the clear feed – deleted reinstalled

    only have 10 items (actual only had 7 when a started 3 days ago) – free version so no variants

    really am struggling to find a solution

    The page I need help with: [log in to see the link]

Viewing 11 replies - 1 through 11 (of 11 total)
  • Thread Starter haychart

    (@haychart)

    hi – i received an email but posted to someone elses thread although relating to mine

    https://www.ads-software.com/support/topic/plugin-working-file-not-changing/

    how do i send screenshots

    i now have 1 processing – although it has been doing that for a while

    have cleared te feed process and ticked / unticked the Automatically fix feeds …..

    Plugin Contributor Michel Jongbloed

    (@michel-jongbloed)

    Hello @haychart,

    Sorry for my late reply.

    Could you tell me if you have the plugins Wordfence or BasicAuth active on your server?

    If you have Wordfence active, could you please try the following steps?
    ?1) Temporary deactivate Wordfence
    ?2) Open the Feed Manager -> Settings page and press the “Clear feed process” button
    ?3) Try to generate a feed
    ?4) Activate Wordfence again
    ?5) Try to generate a feed again.

    Please let me know if that worked, or if you’re using BasicAuth on your server.

    Best regards,
    Michel

    Thread Starter haychart

    (@haychart)

    Hi

    we are using wordfence

    deactivated plugin and a feed was created
    reactivated – regenerated and just went to processing

    have now deactivated – regenerated to get an ok
    now reactivated wordfence so will it still work

    Plugin Contributor Michel Jongbloed

    (@michel-jongbloed)

    Sorry, but I’m not sure if I understand the status of the issue.

    If I read it correctly you now can generate a feed with the Wordfence plugin deactivated, but as soon as you reactivate Wordfence the feeds stay in the processing stage?

    Thread Starter haychart

    (@haychart)

    sorry no

    the feed still says ok – I was just wondering if it would affect it with wordfence activated again

    the answer I think is no as google found my feed but rejected it due to gtin (unfortunately the site is for my wifes jewellery business and we do not use gtin so any help on that issue would be good)

    Plugin Contributor Michel Jongbloed

    (@michel-jongbloed)

    I’ve had some reports that you can activate wordfence again once you have one feed made with it deactivated. Best thing to do is just try it out on your server. See if you still can generate feeds with Wordfence on.

    As for the gtin, I don’t think I can help you there. At least it has nothing to do with the Wordfence issue.

    You could read up in using GTIN in Googles feed specifications which you can find here: https://support.google.com/merchants/answer/7052112?hl=en. If you search that page for gtin you should find a way on how to handle that.

    Best regards,
    Michel

    Plugin Author AukeJomm

    (@aukejomm)

    Hey @haychart,

    You can set identifier_exist attribute to “no” the products of your feed. That way google know’s that there is not GTIN number for those items.

    Thread Starter haychart

    (@haychart)

    i tried that

    google says

    20 errors
    10 ERROR: Invalid GTIN value.
    10 ERROR: Invalid integer in attribute: multipack.

    Plugin Author AukeJomm

    (@aukejomm)

    @haychart, did you fill in the GTIN Make sure it is empty do not fill it just leave it blank

    Plugin Contributor Michel Jongbloed

    (@michel-jongbloed)

    Hello @haychart,

    Have you been able to solve the issue with Auke’s advice? Can we close the ticket now?

    Best regards,
    Michel

    Thread Starter haychart

    (@haychart)

    all sorted thanks

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘still processing’ is closed to new replies.