Forum Replies Created

Viewing 15 replies - 1 through 15 (of 16 total)
  • Another vote to change this. Implying that the SG cache is explicitly storing HTML files in browser memory somehow is confusing, and sent me down quite a time-wasting rabbit-hole!

    @roxannestoltz Just trying to help you out by adding more detail to this bug report, so that you can fix the issue. I don’t need any help.

    I have a different message that I also can’t dismiss:

    WooCommerce Eway Gateway has been automatically updated

    Your store is now running the latest secure version of WooCommerce Eway Gateway. We worked with the WordPress Plugins team to deploy a software update to stores running WooCommerce Eway Gateway (versions 3.1.0 to 3.5.0) in response to a security vulnerability that was discovered.

    Every time I click Dismiss and reload the page, the message comes back.

    Version 3.5.2.

    I was able to delete the audience, recreate a new empty audience, and then reconnect and retry the initial sync. This time, I selected the “Only sync customers in this store who are subscribed in my Mailchimp Audience” option.

    The result was that all of the contacts were added to Mailchimp perfectly, with all of them correctly set to “Non-subscribed”.

    I think perhaps that option’s text is not accurate or not clear. At least, I took it to mean that nothing would be synced, because my Mailchimp audience was empty before the sync. In fact, they were all synced perfectly.

    I’ve just experienced the same issue. On the initial sync, all of the customers have been added with a marketing status of “Subscribed”, even though the WC customers did not opt in to marketing at any point.

    The only other option was: “Only sync customers in this store who are subscribed in my Mailchimp Audience”, which presumably wouldn’t have synced any contacts because the audience was empty at the time.

    Shouldn’t there be a “Sync all the customers, but set them to “Non-subscribed” option?

    https://mailchimp.com/en-au/help/best-practices-for-e-commerce-subscribers/

    I’m seeing exactly the same issue. WordPress 5.7.2, Storefront 3.7.0. No child theme. All plugins deactivated.

    Seems to be one or more rulesets inside storefront/assets/css/base/gutenberg-editor.css causing the issue. If I rename that file then all the headings align correctly.

    Possibly related to this issue.

    • This reply was modified 3 years, 5 months ago by globalmatt.
    • This reply was modified 3 years, 5 months ago by globalmatt.

    I’m seeing the error in PHP 7.2.34 also. It’s because you’re using a trailing comma at the end of the argument list, which is only supported in PHP 7.3 upwards:


    /* translators: 1 is the expiration month and 2 the expiration year */
    ‘expires’ => sprintf(
    esc_html__( ‘%1$s/%2$s’, ‘wc-eway’ ),
    $saved_card[‘exp_month’],
    $saved_card[‘exp_year’],
    ),

    Removing the trailing comma (or upgrading PHP to 7.3) fixes the error.

    • This reply was modified 3 years, 6 months ago by globalmatt.
    Thread Starter globalmatt

    (@globalmatt)

    Also, unless I’m imagining it, Facebook have completely changed how all of this works since I looked at this last week. The Use Cases have gone, and have been replaced by a page called “Ad & Sales Channels”. Again, no option to link to Shop – just Traffic Ads, Dynamic Ads and Instagram Shopping.

    However, there is something called Commerce Manager now – should we be using that instead?

    (Also, I’ve just noticed that the products are now appearing in the Page Shop on the Facebook front end! This has happened even though we didn’t link the catalog to the shop. So I’ve no idea what’s happening but it appears to sort of be working now.)

    Thanks,
    Matt

    Thread Starter globalmatt

    (@globalmatt)

    Hi Julie,

    It’s a Facebook Page with a Shop. It’s a client’s Page, and I’m using his Facebook account to manage the Page and set up the Shop. It’s also the same Facebook account that I used to set up the plugin.

    Please also see my reply in this thread:

    https://www.ads-software.com/support/topic/items-not-appearing-in-facebook-shop/

    As I say, I can create a test catalog using the same Facebook account and that gives me the option to add the shop in Use Cases. It’s only the catalog created by the plugin that doesn’t have a linking option in Use Cases.

    Thanks,
    Matt

    Hi Simon,

    Thanks for your reply. I did do exactly these steps already, but I’ve just done them again as requsted:

    1. Deleted all catalogs from Facebook. This brought up the “Select Your Catalog Type” page in Facebook Catalog Manager, asking me to create my first catalog.
    2. Removed the WooCommerce connection.
    3. Re-addded the connection, selecting the Page to connect the catalog to, and installing the available Facebook Pixel. The popup window informed me that there are 378 Products in my inventory, and the Catalog switch was set to ON (and greyed out). I clicked Finish to finish the setup. I received a Setup Complete message (“You’re now ready to create ads for online sales and add features for your business from Instagram, Messenger and more. Shops and products are usually reviewed within 24 hours.”). I clicked Continue, then closed the popup.

    After a few minutes the catalog reappeared under https://www.facebook.com/products/. However, the Use Cases for the catalog still don’t show a Shop Page option. I only see “Get Started With Dynamic Ads”, “Get Started With Traffic Ads”, and “Get Started With Instagram Shopping”.

    BTW I’ve also had logging turned on for the plugin since I first installed it. Here’s a log snippet:

    
    05-29-2020 @ 15:47:56 - Generating a fresh product feed file
    05-29-2020 @ 15:48:07 - Product feed file generated
    05-29-2020 @ 16:03:59 - Generating a fresh product feed file
    05-29-2020 @ 16:04:10 - Product feed file generated
    05-29-2020 @ 16:19:40 - Generating a fresh product feed file
    05-29-2020 @ 16:19:50 - Product feed file generated
    05-29-2020 @ 16:34:53 - Generating a fresh product feed file
    05-29-2020 @ 16:35:04 - Product feed file generated
    05-29-2020 @ 16:43:04 - Facebook is requesting the product feed.
    05-29-2020 @ 16:43:04 - fpassthru is disabled: getting file contents
    05-29-2020 @ 16:50:54 - Generating a fresh product feed file
    05-29-2020 @ 16:51:08 - Product feed file generated
    05-29-2020 @ 17:06:54 - Generating a fresh product feed file
    05-29-2020 @ 17:07:04 - Product feed file generated
    05-29-2020 @ 17:22:10 - Generating a fresh product feed file
    05-29-2020 @ 17:22:21 - Product feed file generated
    05-29-2020 @ 17:37:59 - Generating a fresh product feed file
    05-29-2020 @ 17:38:09 - Product feed file generated
    05-29-2020 @ 17:44:03 - Facebook is requesting the product feed.
    05-29-2020 @ 17:44:03 - fpassthru is disabled: getting file contents
    

    Thanks,
    Matt

    Thread Starter globalmatt

    (@globalmatt)

    Thanks for your reply Julie!

    I think it’s a business account but I’m not 100% sure. How do I check?

    Plugin version: 1.11.3
    WooCommerce version: 4.1.0
    WordPress version: 5.4.1

    I also tried creating a new test catalog and that catalog did give me the option to add the shop. It’s only the WooCommerce catalog that has the problem.

    Thanks,
    Matt

    Linsday, I have exactly the same problem:

    https://www.ads-software.com/support/topic/cant-create-facebook-page-from-catalog/

    Hoping to find a solution too!

    @bward: I had the same question, so I dug through the plugin source myself and can confirm that it does indeed create the mwp_update_public_keys cron event (in init.php):

    
    // Public key updating cron.
    if (!wp_next_scheduled('mwp_update_public_keys')) {
        wp_schedule_event(time(), 'daily', 'mwp_update_public_keys');
    }
    
    Thread Starter globalmatt

    (@globalmatt)

    Thank you very much! I have just given you access and sent you an email.

    Best wishes,
    Matt

    I’m seeing regular short freezes (every few seconds) when using the TinyMCE editor on Safari 10.0.1. Still running on Mac OS 10.11.6. They’re not as bad as yours, but enough to be annoying while typing. Chrome is a lot better, although there is still the occasional short freeze.

    Edit: This is with WordPress 4.7, but I also noticed it with 4.6.

    • This reply was modified 7 years, 11 months ago by globalmatt.
Viewing 15 replies - 1 through 15 (of 16 total)