aBLOGGERwithoutAblog

Still waiting for a kind answer. 20 days should be enough to answer a quite simple question: has the plugin a string traslation feature as stated in the descriprion? If yes, can I know how to use it?

Excuse me, but I think you’ve completely misunderstood my question. I don’t see any reference to translating strings within a PHP template on the page you linked.

Let me try to clarify my need again: I need to translate some strings present in a PHP template. For example, there might be a string ‘Last articles’ and I would like this to be translated into Italian if the user is browsing the website in Italian.

Ok, I found out that the button appears once the PayPal Card Processing method is disabled. I little strange behavior, to be honest, but it’s totally okay now.

Thanks for your great job and for your kind answer.

Many thanks to both of you.

@corrinarusso , when I write that the filter doesn’t filter correctly I mean that, choosing one of the two options from the dropdown, I’m always redirect to the same CTP single page, regardless the field value matches or not. And it’s true, my loop was doing nothing, but even adding the_title(); nothing changes.

@bcworkz , how did you make it work? I added the_title(); at the loop as you did, but it still doesn’t work… I will deal with the clear filter issue and the validation after I figure out how to make things working.

Because it’s really hard to find a solution online, I would like to share with you a workaround I found.

First of all, we need to deregister the parent style

add_action( 'wp_enqueue_scripts', 'remove_default_stylesheet', 20 );
 function remove_default_stylesheet() {
     wp_deregister_style( 'storefront-style' );
}

After that, we should copy the entire Storefront’s style.css in our child theme’s CSS. At last, we should copy the entire /assets/css/woocommerce/woocommerce.css in our child theme’s style.css too.

To change the breakpoint, search for @media (min-width:768px) and change 768 with the number you want.

I know it’s a workaround, so please share with me other solutions if you have.

• This reply was modified 5 years ago by aBLOGGERwithoutAblog.

First of all, thanks to everybody. As i told you before, I’m not an expert, I learnt some HTML and CSS by myself, and I’m just trying to play with Javascript.

Following your tips, I solved the problem as follow.

I added this to funtions.php:

<?php
//aggiungere funzione cambia_classe_nav
 add_action( 'wp_enqueue_scripts', 'cambia_classe_nav' );
 function cambia_classe_nav(){
 	if(is_front_page()){
   wp_enqueue_script( 'menu-scroll', get_stylesheet_directory_uri() . '/js/menu-scroll.js', array() );
 }
 }
?>

I created a menu-scroll.js like this:

var lastScrollTop = 0;

window.addEventListener(
  "scroll",
  function() {
    var st = window.pageYOffset || document.documentElement.scrollTop;

    if (st > lastScrollTop) {
      
      document.getElementById("navigazione").classList.add("scuro");
    } else {
      
      document.getElementById("navigazione").classList.remove("scuro");
    }
    lastScrollTop = st <= 0 ? 0 : st; // For Mobile or negative scrolling
  },
  false
);

And after all …. it simply works!

Thanks again for your great help.

• This reply was modified 6 years, 1 month ago by aBLOGGERwithoutAblog.

Thank you, and sorry for the late reply.

I can confirm that I use a cache plugin (W3 Total Cache). Anyway, WhatsApp sharing button works great again after updating the plugin.

Thanks for your great job.

Your plugin is a trap, because the free version is completely useless and the user should pay to solve the problem.

I was thinking that your plugin could be time saver for me, but finally I spent few hours more than expected to transfer the updates to the production website because THERE’S NO EASY WAY TO DO IT WITH YOUR PLUGIN. And please, stop saying that you wrote a page in your documentation with the instruction to push changes in the main website, because what there’s written in that page could he easily resumes with 4 words: BUY THE PRO VERSION.

What made me angry is that the description is misleading. I saw the page where you describe the procedure to push changes, but you even not mention that it’s valid just for the paid version! You should just sell your plugin, not creating a trap where the only way to don’t waste hours of work is paying a pro version to the developer. For sure it’s my fault if I didn’t check properly what the plugin was really able to do, but the description is not honest at all.

So, at the and, I can change the words you didn’t like in the previous message: it’s not pointless, it’s a trap.