Forum Replies Created

Viewing 15 replies - 31 through 45 (of 105 total)
  • Thread Starter forkmedia

    (@forkmedia)

    If the images are not being saved “locally,” why are images showing up in my media library visually, but not showing up physically in backups?

    I noticed that the changelog states that version 1.41 “Modified the function that saved images localy to only save as attachments”. But I don’t understand how or where these attachments are stored.

    I installed the latest upgrade to Instagram Slider Widget and changed the settings in the widget from thumbnails to standard. The author changed the defaults in the upgrade. It appears in my case that I also had to wait for whatever the refresh rate I had set – the interval it checks Instagram for new images – to pass before the full number of images I had set appeared. If you see captions without images, reduce the number of images and the refresh rate. Once everything is working, you can increase both settings.

    Thread Starter forkmedia

    (@forkmedia)

    I guess you missed my earlier message in this thread where I pointed out that I had already improved the sharpness by going from thumbnail (150) to 320. I will go to 640 to see if it gets mo’ better.

    I did notice that when I did the update, it DEFAULTED to thumbnail, which is why the images went from sharp to blurry. It kept my other settings so why did it change the image size?

    Thread Starter forkmedia

    (@forkmedia)

    starkravingcat.com – bottom right of page

    • This reply was modified 8 years, 1 month ago by forkmedia.
    Thread Starter forkmedia

    (@forkmedia)

    Patience appears to be the key – tried a few hours later and still wouldn’t show added images. I waited a day and again increased the number of images and now they all show up.

    Scott Evans plugin is definitely not the same. It does work but I didn’t see any options for a slider or any of the many other options offered by this Instagram slider widget plugin.

    I just updated Genesis Connect to 0.9.10 on a test site running Metro Pro and Woocommerce 3.2.6 and products on the Shop Page disappeared. I reinstalled 0.9.9 and the products came back.

    I have no plans to update Woocommerce to 3.3 – have you looked at their changelog?

    They also pissed me off with their new warning about incompatible plugins – almost a full page of real estate on my plugin admin screen that basically indicated all my plugins (all latest versions) were incompatible with Woo 3.3 – including the latest versions of their own Woo plugins!

    Thread Starter forkmedia

    (@forkmedia)

    I got this on my last reply: This post has been held for moderation by our automated system. It will be reviewed within 72 hours.

    Here’s the reply:

    I don’t know anything about cached transients – I have about two dozen plugins on one WP site and about a dozen on the other. All the other plugins I just tested by clicking on the Details link show their changelogs, reflecting them as updated to the latest version. Only yours shows the previous version.

    As far as the screenshot you posted, I don’t exactly have that on my Plugins page – I’m on OSX High Sierra using latest versions of Firefox, Safari and Chrome – not seeing the last two lines. Just the first line under the plugin’s title, with the Details link.

    I’m not seriously concerned at all about this – though thanks for the direct link – it works – but I originally made the comment here because I thought you would like to know in case you had not updated the changelog.

    Signing off – no need to reply.

    Thread Starter forkmedia

    (@forkmedia)

    I don’t know anything about cached transients – I have about two dozen plugins on one WP site and about a dozen on the other. All the other plugins I just tested by clicking on the Details link show their changelogs, reflecting them as updated to the latest version. Only yours shows the previous version.

    As far as the screenshot you posted, I don’t exactly have that on my Plugins page – I’m on OSX High Sierra using latest versions of Firefox, Safari and Chrome – not seeing the last two lines. Just the first line under the plugin’s title, with the Details link.

    I’m not seriously concerned at all about this – though thanks for the direct link – it works – but I originally made the comment here because I thought you would like to know in case you had not updated the changelog.

    Signing off – no need to reply.

    Thread Starter forkmedia

    (@forkmedia)

    When I started this comment I was asked what version I was using – don’t you see that over in the right column?

    In any case its 4.92 on two different sites. One site I updated your plugin to 7.0 and clicked on Details > Changelog. Showed 6.4.8. I also have an update notice on the other site but I didn’t update yet and also checked the Changelog there but it still shows 6.4.8 as well.

    I usually don’t update plugins unless I can see what changes have been made. Last time I updated your plugin, as noted in your Changelog, you updated three times in one day.

    ; )

    I had the same problem after upgrade to 1.41: no photos showing. Before I came to this support page, I just went back to 1.4, which works fine.

    Is there some other compelling reason to upgrade to 1.41? I realize some people had problems, but 1.4 seems to work fine on our site.

    When you say change the number of images, did you mean to a specific number? Any number up to 12? I believe we are currently set to 8 with 1.4. If I simply reset 1.41 to 8, will that work?

    I recently got the Invalid SKU error. I’m not using WPML but if I create a new product and give it an SKU under Inventory or have an old product that has an SKU already assigned, then add variations, and give each variation a different SKU, the error occurs. I usually assign the first variation the same SKU as the original product.

    Once I change the SKU under Inventory to a different number, the error goes away.

    Example: Original product SKU is P0001. Variations: P0001 and P0002. This will generate an error.

    Change Original product SKU to P0000. Keep Variation SKUs: P0001 and P0002.

    No error.

    The error did not happen on earlier versions of Woocommerce but I noticed it after I upgraded to the 3+ versions.

    This may not be the exact same problem as described by some in this thread but I thought it may help those who have may have the same problem as I did.

    Thread Starter forkmedia

    (@forkmedia)

    I have tried a number of css selectors but still haven’t been able to crack the problem of extra space in the storefront header areas as outlined in my post above.

    1. Below the logo and/or Above the primary navigation

    2. The primary navigation’s container height

    Thread Starter forkmedia

    (@forkmedia)

    Finally.

    I took the path out of the exclude code and left just the snapshots directory and it worked.

    Whew…

    Thread Starter forkmedia

    (@forkmedia)

    I added the code in my wp-config and ran a manual backup but the size didn’t change significantly – 458mb vs 460mb. Either the path is wrong or the code doesn’t work.

    I’d love to spend my days troubleshooting your plugin but I don’t have the time.

Viewing 15 replies - 31 through 45 (of 105 total)