Forum Replies Created

Viewing 10 replies - 1 through 10 (of 10 total)
  • Thread Starter trevor67

    (@trevor67)

    For OnePress version 1.3.1:

    I found a .slider-spinner class with a backtick in theme.js. Deleting the backtick fixed the problem:
    hero.find('.slider-spinner').remove();

    Edit the theme files at your own risk!

    • This reply was modified 7 years, 8 months ago by trevor67.
    • This reply was modified 7 years, 8 months ago by trevor67.
    Thread Starter trevor67

    (@trevor67)

    Hi Rumores,

    Thanks for the fix, although I’d hoped an official update would have been released by now. Or at least some acknowledgment from the developer that an update is coming. With so many using the plugin, surely there must be more people affected? For now I’ve just rolled back to the previous version of CF7.

    Thread Starter trevor67

    (@trevor67)

    Okay, now I understand. Thank you for the explanation!

    Thread Starter trevor67

    (@trevor67)

    Hello Jeff,

    Thank you for your reply. I’m sorry I didn’t communicate the broken link issue very well–the link I posted in my question indeed does link to a working page. However, if you go to that page, near the bottom of the page under the heading “Modules” is a hyperlinked unordered list item called “Security.” It is that link which is broken and results in a Page Not Found.
    https://www.jfarthing.com/docs/theme-my-login/security

    I hope this helps.

    Thanks,
    Trevor

    Thread Starter trevor67

    (@trevor67)

    Hi,

    My apologies…a plugin is causing the issue. Which is weird because it is only the archive page which is affected, but nevertheless it’s a plugin problem.

    Regards,
    Trevor

    I just updated to the latest version, today, and I’m having the exact same problem. However, there are no errors in the webserver logs. FYI I’m running multisite. The plugin has worked flawlessly for me prior to this.

    Please advise for any specific information I can provide which may help troubleshoot.

    Thanks,
    Trevor

    Thread Starter trevor67

    (@trevor67)

    Thank you! Sorry for my tardiness…I’ll give Sydney five stars.

    Media queries move some elements to -999em when the site is loaded for smaller screens, thus making them disappear. I agree we can get rid of the small product thumbnail and the product’s price when using smaller screens, but taking away the “remove product” option isn’t cool.

    To have the option present for all sizes of screens you need to put the following CSS snippet in your custom.less file, or if you’re not using LESS to compile your CSS, put the snippet in your custom.css file. Make sure the snippet is BEFORE the media query referring to 768px.

    /*
    GLOBAL STYLES
    —————-
    Add styles beneath this line that you want to be applied across your entire site */

    table.cart .product-remove {
    position: static;
    padding-right:.5em
    }

    I’m posting this with the hope that it will help some of you who are suffering from this crazily frustrating situation. Here’s how I made my problem go away:

    What I wanted configured for shipping was a $5 per item flat rate, with free shipping for purchases of $100+. I’d also set Flat Rate as my default shipping option, and yes, no matter what I kept getting that stupid error. That is, until I named the flat rate. It seems that until you actually define the flat rate with a name it won’t acknowledge it, no matter if you’ve set up how many dollars per item or dollars per order the flat rate is going to be. On the Flat Rate page, underneath the checkbox to enable the Flat Rate, put some text in the box beside “Method Title”. For instance, in a fit of creativity I named my flat rate “Flat Rate”. And there it was–no more error. The name for your flat rate now shows up on the cart page and the checkout page with the shipping total beside it.

    Like I said, I hope this helps someone.

    Thread Starter trevor67

    (@trevor67)

    You, Sir, are a scholar and a gentleman.

    I made the edits, and wonder of wonders, my fat fingers didn’t foul up the deal. Everything works perfectly. The only oddity is that the Page Sidebar won’t display on the Shop page–which doesn’t bother me because the other three sidebars work, so there are lots of choices left.

    Thank you very much, Anthony; I appreciate your efforts. I’ll send you a link to the site once it’s finished.

    Regards,
    Trevor

Viewing 10 replies - 1 through 10 (of 10 total)