paprika27

Joe, thanks, that helps!

So, in order to get WP-Accessibility in a WordPress set to “Deutsch Sie” to be in German I should not dump the incomplete translation from the wordpress translation site into the plugins lang folder. Instead, I should grab the complete translation from the folder /wp-content/languages/plugins/wp-accessibility of a WordPress set to “Deutsch” and put it in the same place in my “Deutsch Sie” WordPress.

This seems so extremely combersome for just two frontend strings. I’ll try anyway.

EDIT: Setting WordPress to “Deutsch” does not cause a wp-accessibility_DE.mo to appear in /wp-content/languages/plugins/. So I can’t copy it to the same place in my “Deutsch Sie” wordpress. Do I need to manually trigger it to download language files for plugins?

EDIT2: Ok, under dashboard>updates it offered me to download additional translations for my WordPress set to “Deutsch”. I did so, mo and po files for your plugin appeared at /wp-content/languages/plugins/. I renamed them to ~_formal and switched my wordpress back to “Deutsch Sie”. Now all is as I expected it to be at the get-go. Thanks for the decisive aid!

• This reply was modified 6 years, 1 month ago by paprika27.
• This reply was modified 6 years, 1 month ago by paprika27.

I just downloaded the plugin from the german wordpress org page. Just like the one I downloaded from within my backend, the folder lang contains no de .mo

I changed wordpress to “Deutsch (Sie)”, which, granted, has a smaller completion level than “Deutsch”. Is there the “Deutsch” .mo for your plugin which I can add to my “Deutsch (Sie)” translation? I had hoped I would be able to get the current translation of your plugin as a .mo file and could dump it into the lang folder. Maybe it needs a different name to be applied?

Thanks!

• This reply was modified 6 years, 1 month ago by paprika27.

what you wrote is exactly how I changed the language of the page.

yes, it should but it does not. Im assuming the reason is that while WordPress is available in de_DE, the plugin folder lang does not have any de files.
And Im assuming that this is due to the incomplete translation. I really only care about the two front end strings so I want to have the incomplete translation anyway but don’t know how.

• This reply was modified 6 years, 2 months ago by paprika27.

pardon, it might well be a problem with my css and not your js. here is the site:
praxislandgraf.de

pagespeed was enabled. now it does what I expect.

the template override was the only way in which I was able to get it working. I’m assuming I got the syntax wrong on the filters.

EDIT: The behavior persists: refresh query or no query don’t seem to look at the override, debug works fine. Can you tell me where the cache

set_transient( $cache_key, $css, 4 * WEEK_IN_SECONDS );

would be located? i’d like to remove it manually.

EDIT: Nevermind, reinstalling the plugin did it. now, without query, override is in effect as desired. I recommend adding this to your wiki as a customization example.

• This reply was modified 6 years, 5 months ago by paprika27.
• This reply was modified 6 years, 5 months ago by paprika27.

waiting a while fixed it. Apparently, refresh_css did not actually touch the cache but time did?

there is no caching plugin installed, browser cache was cleared every try i gave it.

Thanks!

EDIT: I was too quick to conclude: in photo view, it now works without query. in month view I now see the same behavior: it works fine if i query debug, it does not, otherwise. I’ll wait awhile again but it sure is weird.

• This reply was modified 6 years, 5 months ago by paprika27.
• This reply was modified 6 years, 5 months ago by paprika27.
• This reply was modified 6 years, 5 months ago by paprika27.

Sunny Lal has since written to me the following solution to the problem:

{{ event.get( ‘post’ ).post_title }}

Thank you

I changed my searchform to

function add_search(){
echo '<div id="searchwrapper">
		<input type="checkbox" name="toggle" id="searchtoggle" /><label for="searchtoggle"></label>
		<form id="searchform" class="searchform" onsubmit="return false;">
			<label class="screen-reader-text" for="s">Suche nach:</label>
			<input type="text" value="" name="s" data-swplive="true" id="s" autocomplete="off" placeholder="Suchbegriff eingeben">
		</form>
	</div>';
}
add_action('__after_navbar', 'add_search');

to avoid redirection to a queried page altogether (return false onsubmit) and started using searchwp-live-ajax-search plugin as a workaround.

Thanks so much! I was looking for a bug in SearchWP Live Search causing this message. It was actually caused by this Advanced Page Load Plugin “Feature”.

Thanks for your response. I must not have made myself clear.

What is the variable containing the title?

{{ event.filtered_title | raw }} does not work. The link you provided does not help.

(Nice of you to add it to the roadmap but I don’t really care for the list, I just want the title instead of the post_id)

hm. thanks.

this is the dirty work around: https://stackoverflow.com/questions/1987579/remove-warning-messages-in-php

neither am i nor has this occurred before putting your widget there. not helpful at all.

aha, I seem to have to set text-align to center for the div to float to the center? I’ll just css select the .service-desc and move it back left. Odd back and forth though. Is there a more elegant way?

Thanks!