chris29888
Forum Replies Created
-
Well, that explains my confusion 😅
Thanks for clearing it up!Hi!
Sorry for not replying sooner. It sounds really amazing and I’m already super thankful that you addressed this issue.
Unfortunately, I still haven’t had the time to implement the latest updates cause I’ve been swamped with work for the past few weeks. I’ll let you know as soon as I try it out!
Thanks again!Alright, thanks for clearing that up! Looking forward to the update.
Hey, thanks again for getting back to me so quickly!
That sounds great. Borlabs allows the execution of custom JS after a user has given explicit consent, so it shouldn’t be a problem.Still though, and this might be a stupid question, given that I’m not a developer, isn’t it possible to locally embed the 2 files that are currently being loaded via the external CDN? (embed.js and frontend.css)
Wouldn’t it be enough to connect to the Buttonizer servers only while making changes to the currently implemented buttons and then have them create 2 static, local files once the WordPress admin clicks “Save”?Any news on the GDPR front? Buttonizer still connects to cdn.buttonizer.io in the background without giving me the option to disable this / only establish the connection if the user opts in.
Wow, thank YOU for being this reactive!
I just installed 3.0.3 and it actually does work and the button is now appearing on the page (still disabled it again because of the GDPR stuff that I’m still not sure about).For the whole cookie consent stuff I’m using Borlabs Cookie.
It seemed to be the most competent and expansive consent plugin and it’s been doing a great job over the past years with constant updates to keep up with the ever changing clusterf*ck that is the GDPR.Hey, thanks for the detailed response!
I’m no legal expert, but I’ve heard multiple times that as soon as one of those background connections is established, no matter how compliant the company at the other end of the line is, there needs to be a clearly indicated consent by the visitor because their IP is still being transferred to some external domain that isn’t the one they’re visiting right now. In theory this could enable the company behind the hidden connection to do whatever shenanigans are possible by knowing someone’s IP and time of access.
(Again, not a legal expert, but that’s what I’ve come to understand.)The other issue
Unfortunately, there are no cache plugins currently running on the site that could mess with Buttonizer’s functionality.Forum: Plugins
In reply to: [Contact Form 7 Multi-Step Forms] Don’t hide contact form after submittingAlright, thanks!
Forum: Plugins
In reply to: [ShiftController Employee Shift Scheduling] Time off / vacation requestsAlright, thanks!
Glad to hear I was doing it the correct way, then.Forum: Plugins
In reply to: [ShiftController Employee Shift Scheduling] Time off / vacation requestsAdding to this, there should be an e-mail being sent out to the calendar administrator whenever someone submits a draft. Currently, the mail is only being sent to the person creating the draft. This way, the administrator won’t even be notified of the new days off request.
I feel like I’m missing something here, because this seems like really basic stuff and it sounds like people in these threads have been using the plugin for this kind of thing.edit: Uh, I think this is already working correctly and I just got my mail addresses mixed up…
- This reply was modified 4 years, 6 months ago by chris29888.
Thanks for replying!
Disabling all plugins and changing the theme wasn’t an option as it’s a customer’s live website.
Instead, I installed WP Auto Listings on a different WordPress site, used the form builder there and then copied the generated form code over to the site where the fields list doesn’t work.
All good now, I’d say.Understandable. Thank you for your speedy reply and the helpful links!
For anyone looking for a solution to this problem in the future:
The developers kindly shared the solution and allowed me to post it here:The words “new”, “used” and “certificated” can’t be translated because they are values rather than strings within the plugin’s files.
In order to get rid of them, you simply need to add this bit of code to your (child theme’s) functions.php
add_filter( 'auto_listings_conditions', function( $options ) { return [ 'Neu' => __( 'Neu', 'auto-listings' ), 'Gebraucht' => __( 'Gebraucht', 'auto-listings' ), 'Zertifiziert' => __( 'Zertifiziert', 'auto-listings' ), ]; } );(replace the each string with whatever you desire, of course)
Afterwards, go to your Auto Listings settings, confirm the new phrases and open up each individual listing and set its specific condition one more time and hit save.
Works perfectly for me now.
Thanks for helping me out, @autolistings !@autolistings Correct.
If it’s an issue with Loco Translate, it should at the very least show up when I actually edit the PHP files directly.
Maybe one of the files links to a php file that’s hosted on one of your servers and that’s where the untranslateable files come from (just a wild idea though).I’ll give the support ticket a try, thanks!
I managed to display the $condition on the single listing page.
Still hoping for a way to translate it because it’s quite useless otherwise.