waffl
Forum Replies Created
-
Forum: Plugins
In reply to: [WP REST Cache] skip_cache returns endpoint description instead of dataMy sincere apologies, I’m actually using the confusingly similarly named but different ‘WP REST API Cache’ Plugin which hasn’t been updated in some time.
I’ve actually moved to this plugin now and everything is working wonderfully!
Forum: Plugins
In reply to: [WP REST Cache] skip_cache returns endpoint description instead of dataOk, it’s back. For some reason, this keeps happening at some point and goes away once I click
Empty WP REST API Cache- This reply was modified 6 years, 8 months ago by waffl.
Forum: Plugins
In reply to: [WP REST Cache] skip_cache returns endpoint description instead of dataHm, actually flushing the cache completely seems to have made it work again, I will report back in case the problem reappears.
Forum: Plugins
In reply to: [qTranslate X] Can't get ACF to work with qtranslate-X@funkjedi – My endless thanks for stepping back in, your plugin is without doubt a far superior solution and I can confirm it’s working perfectly for me. Very happy about this!
WordPress 4.1.1
ACF 5.1.9.1
qTranslate X 3.1Forum: Plugins
In reply to: [qTranslate X] Can't get ACF to work with qtranslate-X@johnclause I’ve also setup a completely fresh install of WordPress with latest ACF, qtranslate x, and my plugin; the language toggle still only affects the first custom field.
I’ve also updated the class name to avoid hyphens
acf_field_qtranslatex_textareato no avail, any ideas why this might be happening?I’m trying to dig through the javascript but can’t seem to find a solution, all the code seems logical from me through the process in
common.jsofaddDisplayHooksByClasstoaddDisplayHookstoaddDisplayHook…There are no errors thrown on the console either. Any tips or direction would be so deeply appreciated, somehow the state of multilingual functionality in wordpress seems so convoluted since qtranslate was abandoned and I’m happy to work towards a well maintained project finally.
Forum: Plugins
In reply to: [qTranslate X] Can't get ACF to work with qtranslate-XOk, well I couldn’t really wait too long and all I need currently for my purposes was a translatable textarea.
I wrote a really quick plugin for anyone who needs a translatable text area with ACF 5+ and qTranslate X 3+
https://github.com/alancwoo/acf-qtranslate-x-text-area
—
@johnclause Hm, okay frustratingly somehow with more than one textarea field, even though the class is now the same, only the first field seems to be working, any ideas from the -x side of things?
Forum: Plugins
In reply to: [qTranslate X] Can't get ACF to work with qtranslate-XHm, I’ve also now tried cleaning up the selector like so:
div[id^=acf-field_]but it still doesn’t work.
I have a feeling it may be a conflict with the way this field is implemented, from this quote just below:
The input fields of type ‘textarea’ will be parsed using <!–:–> syntax, while single line text fields will use [:] syntax. If you need to override this behaviour, prepend prefix ‘<‘ or ‘[‘ to the name of the field to specify which syntax to use.
Forum: Plugins
In reply to: [qTranslate X] Can't get ACF to work with qtranslate-XI tried to use a wildcard CSS selector, which should work as I’ve tried in this jsbin:
http://jsbin.com/bokazuzutu/1/
However, when I try saving this as an ID name in the -x options, it doesn’t save (it’s escaping the quotation marks).
Maybe this is the simplest fix if we can solve this escaping issue?
Forum: Plugins
In reply to: [qTranslate X] Can't get ACF to work with qtranslate-XAlso having the same problem.
I was using acf qtranslate to create multilingual ACF fields. Qtranslate x seems to take a whole different approach to the way editing works (full-page language switcher rather than per item).
Finally, adding a new plain ACF field (‘text’), the field retains the same content regardless of the language.
—
The ‘class’ or ‘id’ option also doesn’t help because the ACF text inputs have unique classes and id’s per post
eg, the same input will have the class
acf[field_54eb11948d1d4]for one andacf[field_53c66ccc92eb7]for another.To be clear, if I manually input the ID, it works properly, but I can’t possibly manually enter the ID of every single input field for each new post.
—
ACF 5.1.9
qtranslate-x 3.1 (function compatibility ON)
acf qtranslate 1.4Forum: Plugins
In reply to: [qTranslate] qtranslate crashes with WP 3.9.1Can also confirm this fixed the problems I’d been having in 3.9.1 as well.
Would it not make sense to move qtranslate over to a git repo where we can keep a consistently working, community version up to date?
🙁 I hate to ask here, but any chance of a quick paid consultation? I will gladly share the answer here afterwards and definitely value your time too. I’m just really at my wit’s end trying to solve this.
Hi James! Thank you so much for getting back to me!
Yes, I’ve set the cookie paths to be the same, so what is odd is this example:
Magento: Viewing shop in German (de), click to wordpress Area
WordPress: Look around, click on English (en)
WordPress: Magento block loads, but in German (de) – Cookie is set to English (en) as confirmed in Chrome’s resource inspector.
WordPress: Reload page, Magento block loads in English (en)So it’s just something odd about the load order, it seems like the Magento block is getting rendered before WordPress changes the cookie somewhere in the load process (even though I’ve hooked it in before the actual loading of plugins?)
So strange it works just after one reload.
Note:
I’ve even tried moving the qtranslate plugin to mu-plugins and hooking into the muplugins_loaded action which should technically be the first thing happening, yet it still requires a reload before pulling the menu in the right language. Strange.
I can confirm this works for me as well.
I’m using WordPress 3.4.2 and ACF 3.5.0
Works, but is a super hackish way to have to edit a core file like that. I’ll post this to the ACF support and hopefully Elliot can shed some light on it.
edit: Posted a link on this ACF discussion – http://support.advancedcustomfields.com/discussion/comment/9378#Comment_9378
Forum: Plugins
In reply to: [WPaudio MP3 Player] [Plugin: WPaudio MP3 Player] Abandoned?I was having troubles getting it to work after updating to WP 3.2.1/3.3 with Chrome/Safari, and after some tweaks and help from various threads I managed to fix everything as far as I can tell.
Take a look at this discussion and see if this updated code works for you. Todd, if you are reading, maybe you can simply update the plugin as it was only a few small changes. I really didn’t want to find another plugin because as everyone has been saying this one was the best, so thanks a lot for the hard work 🙂