kiddhustle

Hi I remember looking over this recently.

A colleague has since taken over the project, but I think in my case changing the action hook to: parse_query (maybe send_headers) would have solved my problem. My colleague implemented an .htaccess solution outside of WordPress so never had a chance to try it personally.

Yes using the user agent groups should work in W3TC but there are other caching plugins that will overwrite/cancel the redirect..

Like I said I am no longer on the project but my guess is that this is the right place to to detect the user agent and redirect and because the you should be able to detect the user agent and no headers should have been sent yet.

If you get a chance to try this please let me know, could come in handy in the future.

Hi

Just ran a quick test and I changed the label variable from $valueLabel to $valueLabels and the SELECT box worked as expected.

I had a quick look at the code and in some places $valueLabel is used and some places $valueLabls is used. I guess $valueLabels makes more sense as a variable name but just need to make sure it’s the same for all field types and in the documentation.

Could you let us know if we should definitely use valueLabels from now on?

Cheers!

Oh, this is a SELECT element I’m generating not a CHECKBOX so I think make_select() is function involved (line: 1764)

Maybe it could be that some other plugin is conflicting with this one? I’m not sure I can have a look at the code and try to see if there is anything in other plugins/theme that might cause problem..

Hey Vladimir

Nice fix!

Yea.. How does this plugin switch the post type without that code in there? Trippy..

Just to be clear..

This code goes in the two files: RCCWP_Application.php and RCCWP_CustomWritePanel.php. Do they need to go in a specific place or anywhere in the code?

Thanks