awlizw

Since three weeks on the part of the producers of Molongui puzzlement dominates, what actually is the problem, I can already communicate a partial solution for the 1.) guest name problem and the second language of author.php template. Insteat of placin a common function like the_author() I tried to set:
add_action( ‘init’, ‘molongui_get_queried_object’ );
function molongui_get_queried_object() { $obj = get_queried_object();
$displayname = $obj->display_name; echo $displayname; }
echo molongui_get_queried_object(); For me it works at least to see the right guest author name for the second language, and not a wp-user name.
Both kinds of author types use the single author.php template but the return of the guest_author puts a wrong value in the second language. Also I tested a change in the molongui class-guest.php ‘_molongui_guest_author_display_name’ => $_POST[‘post_title’] at some keys and values. Another thing to solve is to use separate templates for author.php and guest_authors.php or to use a language difference with author-de.php. So far my intermediate state with the template for authors. Please Molongui-Team, check your code with class-guest.php public function quick_add(), this is not working bilingual also not for more languages. ‘post_title’ => $_POST[‘display_name’] this seem not to work, because post_name is the slug and post_title is the real name for both languges. The key display_name in the object returns a wrong value. Please check it out with WPML, thank you much. We looking forward for an update of the plugin. We have a lifetime Pro Version of your plugin and we have a complaint.