Forum Replies Created

Viewing 15 replies - 16 through 30 (of 75 total)
  • Thread Starter fesarlis

    (@fesarlis)

    I placed the following on my child theme’s functions.php:

    add_filter( ‘wpseo_json_ld_output’, ‘__return_false’ );

    Thread Starter fesarlis

    (@fesarlis)

    That is great but I am guessing people will not consider it as a solution. Thanks anyway

    Btw, the suggested method to remove schema does not work (at least in my case). Schema data are still there.

    After searching I have found a way that seems to work:

    function my_remove_yoast_json($data){
            $data = array();
            return $data;
    }
    add_filter('wpseo_json_ld_output', 'my_remove_yoast_json', 10, 1);
    • This reply was modified 5 years, 5 months ago by fesarlis.
    • This reply was modified 5 years, 5 months ago by fesarlis.
    Thread Starter fesarlis

    (@fesarlis)

    I understand. However the whole concept still remains IMHO. Not all WordPress sites are blogs. No need to include any kind of author info in that case, so it should at least be configurable. I have also noticed that many users reported this but the team does not seem to be taking it under consideration.

    In any case thank you for your fast reply.

    • This reply was modified 5 years, 5 months ago by fesarlis.
    Thread Starter fesarlis

    (@fesarlis)

    I agree with hskokanek. As far as Woocommerce is concerned, the whole point in using this plugin is prevent simple customers from accessing the dashboard (even if they have no permission to do anything). To put it in another way, what is the point of hiding the login URL if ANYONE can register as a customer and see it?

    My workaround is to disable wp-admin and wp-login.php in web server level. The reason I am using this plugin is because of a side-effect it has. If I don’t use it, customers cannot logout using the logout endpoint of WC. The endpoint obviously uses wp-login.php and they get a 403 error because they are blocked on server level. It is worth noting that this behaviour did not occur in older versions of WC (eg. 2.2). By using this plugin, and perhaps because the URL is changed, customer logout still works.

    • This reply was modified 5 years, 7 months ago by fesarlis.
    Thread Starter fesarlis

    (@fesarlis)

    Thank you for your detailed reply. I have forwarded the details you asked,and also included a new issue I have encountered.

    Thread Starter fesarlis

    (@fesarlis)

    Thank you for your reply. I understand what you say.

    Let me clarify: I am experimenting with EZ form calculator to create a custom form using ez form creator for my products. One of the issues I am facing is this.

    My theme (flatsome) has a floating cart on the RHS of the screen.

    The thing is that if I am to use the custom form, EZ form calculator will hide the default ‘Add to cart’ and add its own.

    However, its options include two SPECIFIC options for this case. I quote:

    – Update mini-cart after adding products (Please note that you use the correct CSS selector or the cart will not be updated.)

    – Cart CSS selector (The mini-cart CSS selector can change depending on your theme. If you are not sure, you might want to contact the theme author.)

    Both you and the theme developer replied that you use the default classes. Still the form’s add to cart does not update neither your cart nor the floating cart.

    As I previously mentioned, I have a partial solution. Using the selector widget_shopping_cart_content the floating cart is updated partially. So the class must be wrong.

    I just want you to provide this selector (even if it is the default WC one) and/or if you understand my config now to pinpoint where the problem might be, ASSUMING that the option above works as expected. Theme’s floating cart is great. That said, I prefer to use your plugin to show added products instead.
    Thanks

    • This reply was modified 5 years, 7 months ago by fesarlis.
    • This reply was modified 5 years, 7 months ago by fesarlis.
    • This reply was modified 5 years, 7 months ago by fesarlis.
    • This reply was modified 5 years, 7 months ago by fesarlis.
    Thread Starter fesarlis

    (@fesarlis)

    Thank you for your fast reply.
    Indeed, for some reason there were duplicates there. So I removed all strings for ‘WP endpoints’ section and translated again, now it works. Thank you.

    One more issue. Please let me know if I have to open a new thread.
    Status shows untranslated products even though there aren’t any. I even tried to remove ALL products (all languages) and the status still shows untranslated products. Any idea what is causing this?
    Thanks again.

    Thread Starter fesarlis

    (@fesarlis)

    Thank you for your reply.

    I was able to solve this by commenting out line 509, like this:

    //add_action(‘wp’, ‘eurobank_message’);

    Now the message appears only once. Perhaps it is also being outputted in some other place in the code?

    Please let me know if you need further information.

    Thanks again.

    • This reply was modified 5 years, 8 months ago by fesarlis.
    • This reply was modified 5 years, 8 months ago by fesarlis.
    Thread Starter fesarlis

    (@fesarlis)

    Thank you for your reply.
    Will have to look it further. Have not examined the code yet. I will come back as soon as I have more info.
    But just to provide a temporary workaround. Can you provide some guidance to exclude specific custom post types from your plugin?

    The first interface (before this one and before the short period of the previous one) was the best.
    This one is far less colorful that can be confusing, and VERY slow.

    Thread Starter fesarlis

    (@fesarlis)

    I see. In such a case IMHO you should at least mention this under each CSP setting because it does not seem obvious ??

    Thanks

    Thread Starter fesarlis

    (@fesarlis)

    I understand. However it seems kind of strange that enforcing CSP will mess WP’s admin interface. We’re not talking about the frontend here, which would obviously be the webmaster’s responsibility.

    In any case, and as I do not consider myself a CSP expert: does your plugin give me the ability to exclude admin interface (or even the whole site) somehow? Just using ‘self’ does not seem enough.

    Thank you

    Thread Starter fesarlis

    (@fesarlis)

    Issue remains.
    WC = 3.1.1
    WCM = 4.2.1

    Thread Starter fesarlis

    (@fesarlis)

    Buttons are sometimes needed, that’s why. To be more precise, I only want those buttons removed for specific user roles. For example, I have content editors for the site that should only be able to create text-based posts. Those users should only be able to see basic text-editing buttons, not buttons that enable them to add an advanced grid or an iframe.

    Thread Starter fesarlis

    (@fesarlis)

    sure.

    Συνελ?φθη μεσημ?ρι, στη

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