phalancs

Hey Josh, thanks for the official reply.

There is just one issue with the “*|SP:CONFIRMLINK|*” I forgot:

Whenever I want to use it right within the HTML it gets cut off and I cannot use it on a an image button for example. I want it to render the link within the “href” but then it wont be rendered properly because the first two characters get cut of ??

Maybe this might be the most important issue about this.

Thanks for your ongoing support nontheless ??

Thanks. Found this as well. And I am sure I have found a solution for the second thing also. Because there is a change date that is logged when someone changes the status. So this is going to be ok I guess. It can only be seen in the right table in the database but it is there. Still the IP is not logged. But I guess that’s OK.

Thanks! Appreciate the transparency, very professional, will do ??

I mean that Um should add an option to ANY widget to controll visibility just like within the menu items.

I have found itand it is clearly stated: “Prevent the loading the core CSS styles. When selected, the appearance options from above will be ignored.”

There was checkbox that prevented the loading of CSS, If this is checked. none of the other settings work. i simply ignored the advanced section. Sry, maybe there should be a hint on to?p where the theming settings are located. Or this css checkbox should not be checked initially.

What???

You should use the post id not the post name since these cannot change.

Same here. Especially happens with theme settings and db saved custom css. Strange error.

I can confirm that I use the German version. Thanks in advance for your effort.

Unfortunately in the bookings overview the format ’25 July 2013′ appears just as shown in the preview without a dot after the date (though that is set in the global wordpress settings). Maybe you could add another date format (d. F. Y.) oder an option “use wordpress default”.

Thanks in advance for your support. Will consider upgrading to pro since I like the sleek nature of the plugin.

And btw: With the second question I just meant that if the email sent to the admin could use a “reply-to” field that is preset with the guests email. So when clicking on “reply” you dont accidentally send an email to yourself ??

• This reply was modified 7 years, 4 months ago by phalancs.

Thank you very much. These formats are nothing I can use to display dates. The first one is missing a dot (d. M YYYY) and those others have an uncommon (in europe: wrong) syntax.

Why don’t you just offer to use the regular correct date format globally set and used in the settings? or preferrably let us just enter the php definition (“d. F Y”).

??

Thank you! Guided me into the right direction. Here is an even simpler and generic solution to naming weirdness:

function rename_flamingo() {
    
    global $menu;
    
    foreach($menu as $key => $item) {
      if ( $item[0] === 'Flamingo' ) {
          $menu[$key][0] = __('Anfragen','textdomain');     //change name
          $menu[$key][3] = __('Adressbuch','textdomain');   //does not work but should (needs another hook?)  
          $menu[$key][6] = __('dashicons-id','textdomain'); //change icon
      }
    }
   return false;
}
add_action( 'admin_menu', 'rename_flamingo', 999 );

• This reply was modified 7 years, 6 months ago by phalancs.

Your question title is the worst ever. And I dont understand your question either.

Resolved. Thank you so much ??

Got it working. Steps:

1. Create the necessary po mo files by using the given sidebar-login.pot file in sidebar-login/languages
2. upload both new files to: your-theme/languages/sidebar-login
3. add the following code to your your-theme/functions.php

function my_child_theme_locale_awe() {
    $my_theme = wp_get_theme();
    load_child_theme_textdomain( 'sidebar-login', get_stylesheet_directory() . '/languages/sidebar-login' );
}
add_action( 'after_setup_theme', 'my_child_theme_locale_awe' );