Forum Replies Created

Viewing 15 replies - 16 through 30 (of 105 total)
  • Thread Starter forkmedia

    (@forkmedia)

    It gets weirder.

    Now WooCommerce PDF Invoice is skipping my custom template when Firefox, ignoring the General settings, downloads the invoice.

    But this new behavior occurs in Chrome as well.

    It’s probably something else on this computer that’s causing this. I’ll have to try the plugin on my laptop and see what happens.

    Thread Starter forkmedia

    (@forkmedia)

    Okay, this is weird.

    Today it’s happening again and the Matomo plugin is not activated.

    I turned a few other plugins off and that didn’t fix it either.

    Since pressing the PDF Invoice button works correctly in Chrome, and a few days ago it worked in Firefox (as well as yesterday after deactivating Matomo), I’m really at a loss. I have not added or updated anything else in Firefox or Woocommerce.

    When I click either the PDF invoice or Packing Slip button, the item automatically downloads despite the setting asking WooCommerce PDF Invoice to open the browser.

    Yesterday I turned off Matomo, the only plugin that had updated since the last WooCommerce PDF Invoice update, and WooCommerce PDF Invoice worked correctly – I tested it several times to make sure. But not today. This kind of irrational behavior in software makes me CRAZY.

    Thread Starter forkmedia

    (@forkmedia)

    I first tried going back to an earlier version of WooCommerce PDF Invoices, but that made no difference. I then tried Chrome and WooCommerce PDF Invoices worked normally. Now I was really confused.

    Your suggestion about the other plugins was also my next plan and thankfully that solved it.

    I just now let the developer of Matomo know about the conflict.

    Thread Starter forkmedia

    (@forkmedia)

    The only other plug-in that updated after yours was

    WP-Matomo Integration
    aka
    wp-piwik.1.0.24

    I deactivated WP-Matomo Integration and WooCommerce PDF Invoices is back to working as expected.

    I don’t use Matomo anymore and forgot it was still activated and updating.

    Thanks!

    Thread Starter forkmedia

    (@forkmedia)

    Thanks for trying to help but I wrote in my original post above that I already did that.

    Thread Starter forkmedia

    (@forkmedia)

    Thanks, the new code worked!

    Thread Starter forkmedia

    (@forkmedia)

    In the style.css file in my theme’s directory, the body tag had a line height of 1.625. The line-height appears in the main page content except the top of the right hand “widget” sidebar where I had specifically changed it to 1. It’s essentially a caption and I wanted the line spacing tighter.

    I added your snippet to the CSS file – nothing changed on the sliderm which is at the bottom of the right side widget column. I also added the !important tag and still nothing changed.

    .jr-insta-caption
    {
    line-height: 1.2 !important;
    {

    I then changed the body css line-height to 1.5 and almost everything changed, including your Social Slider widget, but NOT the text at the top of the widget sidebar, which is set to line-height: 1.

    I am completely baffled.

    More baffling is that when I go back to Social Slider 1.5.0, the slider inherits the widget’s CSS of line-height: 1, ignoring the body CSS. With version 1.5.0, I didn’t need the .jr-insta-caption snippet – which is the way it’s always been until 1.6.0.

    Thread Starter forkmedia

    (@forkmedia)

    1.6.2 is still not working the same as 1.50 and earlier. It appears the Instagram post text is either using new CSS or its inheriting CSS from the page the slider is on. It does not seem to be inheriting it from the column “<div>” where the slider is located.

    If there is a quick way to alter the line spacing using CSS, please let me know which CSS file I need to change.

    See a visual explanation here: https://imgur.com/a/mOyvzH6

    If I can’t change it, I may go back to 1.5.0.

    Thread Starter forkmedia

    (@forkmedia)

    Since someone already reported a problem with 1.6.1 and then 1.6.2 I think I will wait a few days or more before updating. I feel another version may be on the horizon.

    I do want to thank you for responding quickly and for updating your app.

    We do love Social Slider Widget!

    Thread Starter forkmedia

    (@forkmedia)

    I had been using a different WordPress backup plugin that recently changed hands and is no longer actively supported.

    I still use it though, and it sends me a link to every backup, which I can click and easily download. There are no problems due to “technical and security reasons.” I also have it set to delete older backups so there is no problem with storage.

    Now I have backups stored locally as well as on the server AND I back up that to a portable external drive. Cloud accounts generally cost money once you start storing GB’s of data. Their security isn’t perfect either, based on years of stories about cloud sites, including Amazon S3, getting hacked as well.

    I don’t understand this: “you wouldn’t want your backup files in a directory that anyone could access and download with a link.”

    But they are in a directory that can be downloaded via FTP. You still have to have access. If the link is being sent to me, then I’m the only one with that link. If someone can intercept or hack my email, I have bigger problems than someone stealing a backup.

    Thanks for taking the time to respond.

    Thread Starter forkmedia

    (@forkmedia)

    That’s exactly what I DON’T WANT TO DO.

    Is this a hard concept to understand?

    I do not want to send the backup to the cloud. I thought I wrote it clearly in my original message.

    I assume from your answer Updraft can’t do that.

    Though I can’t understand how Updraft can send an email with the backup attached (if its small enough) but not simply send a link to the backup location so one could download it directly.

    Yes, I can go find the backup and use FTP but why are those extra steps necessary?

    Thread Starter forkmedia

    (@forkmedia)

    I always had Stripe as a backup so I just switched over to Stripe and didn’t look back. Stripe also offers Apple Pay and I’ve noticed an uptick in orders, many of them using Apple Pay.

    Thread Starter forkmedia

    (@forkmedia)

    A few hours later the slider returned. Don’t know if making changes outlined in my original post needed to “kick in” or whether it was an Instagram problem.

    I do note that the number of photos showing doesn’t match the updated number in the slider settings (I changed it to 10). Maybe that needs to wait for the next update too.

    Thread Starter forkmedia

    (@forkmedia)

    OK, I upgraded to 1.43 (didn’t realize there had been another update so soon) and saw the button to add images to library, which was on by default. Turned it off and we’ll see how it goes.

    Thanks.

    Thread Starter forkmedia

    (@forkmedia)

    I now see that the image URLs point at Instagram — but the images are still showing up in my WordPress Media Library. I have a rotation of my most recent 10 Instagram photos. As new photos are added by the slider, the old ones remain in the library. Is there a setting to automatically delete those old ones from the library?

Viewing 15 replies - 16 through 30 (of 105 total)