Forum Replies Created

Viewing 15 replies - 1 through 15 (of 121 total)
  • Thread Starter Lyk

    (@lyk-1)

    That would be nice.

    Thank you!

    Thread Starter Lyk

    (@lyk-1)

    Hello,

    tried saving the setting in all pages of the plugin. Some errors keep spamming the logs

    Thread Starter Lyk

    (@lyk-1)

    Καλησπέρα @theogk !

    Έχεις δίκιο για αυτό του woo, μου έκανε και εμένα περίεργο αλλά όντως έσβηνε αυστηρά μαξ 20 και δεν νομίζω να ήταν θέμα της συγκεκριμένης εγκατάστασης. Τυχαία το παρατήρησα όταν είδα να έχει ξεφύγει λίγο ο αριθμός και να μου έχει κρατήσει παλαιότερα του 1 μήνα που είχα όρια. Λίγο που το είχα ψάξει τότε, είδα ότι είναι κάποιο μάλλον hardcoded όριο του WC/WP αναφορικά με το σχετικό νούμερο. Θα το ξαναδώ όμως και στον κώδικα και ίσως σε κάποια clean εγκατάστασταση.

    Τα ξεχωριστά logs έχουν σίγουρα τα πλεονεκτήματά τους, όπως και τα μειωνεκτήματά τους, πχ αν τρέχει κάθε 10 λεπτά θα βγάζει 144 logfiles τη μέρα.

    Αναφορικά με τα filters, η αλλαγή μου είχε γίνει στην λογική να μην υπάρχουν μελλοντικά conflicts με διαφορετικά μελλοντικά feeds όπως λες, αλλά και για να μην βρίσκεται το αρχείο στο default path. Δηλαδή να μην μπορεί κάποιος να βλέπει τόσο εύκολα το feed απλά επειδή είναι fixed το path /wp-content/uploads/dc-export-feeds/skroutz.xml. Αυτό γενικά το θεωρώ λίγο περίεργο, ίσως θα έπρεπε να έχει και κάποιο random part.

    Ευχαριστώ για τις διευκρινίσεις! Υποθέτω η αρχική λογική ήταν για 1 feed, οπότε το UI/στήσιμο είναι βασισμένο σε αυτό και καθώς εξελίχθηκε το plugin, κάποια θέματα δεν καλύπτονται με τον ιδανικό τρόπο.

    Keep up the good work, καλή συνέχεια!

    I checked the PayPal button for WooCommerce PayPal Payments and the plugin seems to cover it just fine.

    If you use the invisible Cloudflare widget, you can temporarily (or use a staging env) use the site key 2x00000000000000000000BB This is an always-fail key, so that you can see how your eshop behaves on the various action when verification fails.

    It’s because the emails are indeed being sent. But most likely the receiving server drops them completely without even putting them in the spam folder.

    This usually happens due to misconfigured SPF/DKIM/DMARC DNS records related to the email you are trying to send from. You should look into fixing these.

    There are quite a few free online services that provide you with a temp email address where you can send an email and check what is problematic with your DNS setup.

    Thread Starter Lyk

    (@lyk-1)

    Hello!

    You are welcome about the description correction.

    I see, thank you for the clarification about the versions.

    For those interested in adding that taxonomy and are comfortable with coding, feel free to check the filter berocket_filter_filter_type_array, with it you can basically add the native Brands taxonomy if needed.

    Thank you for the help and keep up the good work!

    Thread Starter Lyk

    (@lyk-1)

    I see! Thank you for the reply.

    Thread Starter Lyk

    (@lyk-1)

    Ok nice.

    I wasn’t sure what the request to https://static.addtoany.com/menu/sm.25.html#type=core&event=load is about. That’s why I wanted to verify.

    Thread Starter Lyk

    (@lyk-1)

    Thank you for mentioning that.

    So if the external request to https://static.addtoany.com/menu/sm.25.html#type=core&event=load is blocked, it is ok and not expected to cause any functionality issues with the plugin?

    Thread Starter Lyk

    (@lyk-1)

    Thank you for the confirmation, have a nice day!

    Thread Starter Lyk

    (@lyk-1)

    Hello!

    All locations are created from the plugin options, under the location tab. Same for Marker Categories. Are these stored in the postmeta table as well?

    Then on some pages, we just use the shortcode of the corresponding maps, e.g. [put_wpgm id=X].

    So I guess it is safe to just delete the meta entries?
    Last but not least, I believe that some post types, like products and posts, should be excluded by default, so that no empty postmetas are created. By default creating empty data for every post type instance can be very expensive for large installations.

    Thread Starter Lyk

    (@lyk-1)

    Thank you for your replies.

    I mostly agree with the overly fearful lawyers part. Still I believe external requests are best to be avoided unless strictly necessary. Reasons range from performance and security, to reliability and availability if the dependence is strong.

    From what I can tell, there are no plans to change this for the AddToAny plugin, so I am closing the topic.

    Thank you!

    Thread Starter Lyk

    (@lyk-1)

    Hello and thank you for your reply.

    Q1: Is there any way to disable these external requests? If not, are there any plans of doing so in the future?
    Regarding the cache, as already mentioned, it does not eliminate all the 3rd party requests from the visitors browser.

    Q2: Performing a 3rd party request without user consent is a potential GDPR violation.
    The visitor’s IP is exposed to the 3rd party without the visitor ever agreeing or doing any action to justify the exposure of that personal data (IP in our case).

    We had legal departments from various companies mention such restrictions pretty specifically.

    The plugin is great but this area needs some investigation.
    Thank you!

    Thread Starter Lyk

    (@lyk-1)

    Hello and sorry for the late reply.

    Ok, I wanted to verify that even the default query string are not supported.

    Yes, we were using Disk Enhanced so query strings had to be entered as an exception.

    In any case, we’ll be switching to urls without the parameters in order to make sure that everything works fine.

    Thank you!

    Thread Starter Lyk

    (@lyk-1)

    After communicating the the support via their site form, the issue got resolved.

    The fix is now implemented in the latest public version of the plugin.

Viewing 15 replies - 1 through 15 (of 121 total)