efrap

Simply trying to list some categories. This won’t work:

<ul>[terms]
<li>
[term_name]
</li>
[/terms]
</ul>

Error in twenty-fourteen theme:
Warning: in_array() expects parameter 2 to be array
wp-content\themes\twentyfourteen\inc\featured-content.php on line 313

My coding skills are limited, but I just found a simple way to achieve this by replacing brackets with character entities with this simple function:


function qtx_bypass($string){
$string = str_replace("[","&#91",$string);
$string = str_replace("]","&#93",$string);
echo $string;
}


Frontend language buttons would be great, but in the meantime I can have BP members somewhat easily modify and save multilingual BP group info using qtransx brackets on the front end, if they so choose. Will look into using this elsewhere in BP and beyond.

Sorry, my last comment was unrelated with previous topic

Followup:

Is there a way to prevent string from being decoded on frontend?

If the full string was displayed in name input of the frontend edit group buddypress page, I could at least have members enter codes to input multilingual titles.

Every way I try to print group name there, it it always translated.

Another possibility: prevent radio/checkbox html value=”” from being filtered and translated. Used Firebug to test this, works – but I don’t know how to implement it yet.

From what I can now understand, on frontend member form save, buddypress xprofile checks radio/checkbox values against backend values which are encoded and do not match frontend translated values, producing the error. In fact, if other matching non encoded radio/checkbox values exist in backend, they will be selected instead and no errors returned. Maybe I can try disabling that check function in xprofile, or can some JSON integration solve this?

Thanks for your quick response. I really like this plugin. I have no experience with integration yet, but I did manage to quickly add language buttons to the xprofile edit page – never thought I would even get this far! I really don’t mind using encoding, but the problem occurs when saving the options as a buddypress member on the front end (it does work in backend!) – will more json integration help with this? I believe it may not.

You can manage some of this by giving the .wp-tiles-tile class an overflow hidden and 0 height, and a default height for its container.

.wp-tiles-container {overflow:hidden;min-height: 370.85px;}
.wp-tiles-tile {overflow:hidden;height: 0;}

However, page loading is still clunky. It would be nice if tiles were inserted once ready, without slowing down other page elements.