DanielJ7

Yes, that is correct. Auto-translation happens IF the area on the Settings page is left blank (with your default text) AND the translation is available in the po-mo files.
Once a user inserts their own customized text in the settings area, then the auto-translation does not happen for that field.
I have changed the po-mo ES files to include the translation for the Privacy checkbox text, since this had not already been included, and that text did not autotranslate. However, I had no requirement to use custom text there.
I imagine I could have done the same with the Cpatcha label text (just changed the strings in the GB and ES files), but I preferred to use the shortcode attribute for that, so the website owner could change that text to their liking (in both languages).
Thank you for your replies!

• This reply was modified 6 years, 10 months ago by DanielJ7.

Hi Guido,
Thank you for your reply.
If I leave the labels, in settings page, blank (with your greyed out default text), they automatically translate when your contact form shows up.
However, if I want to change a label from its default values (and the ONLY one I need to change is the captcha label, since people find the default version confusing), and I type in the new label in the settings page, then that does NOT translate ??
This is why I would want to be able to set the captcha label via shortcode attributes, as opposed to via the settings page.

I solved this ??

This is what is needed:

Edit the SlideShowPlugin.php file, found in the “classes” directory of this plugin.

Find this string by searching for the word “admin”:

admin_url(‘admin-ajax.php?action=slideshow_jquery_image_gallery_load_stylesheet&style=’ . $styleName),

replace with this:

‘/home/username/public_html/wp-admin/admin-ajax.php?action=slideshow_jquery_image_gallery_load_stylesheet&style=’ . $styleName,

where /home/username/public_html/wp-admin/ is the full path, on YOUR SERVER, to your wp-admin folder. Basically, we are replacing

admin_url(‘…..’)

with

‘PATHTOWPADMIN/……’

i.e. place it ALL inside the single quote, and remove the parenthesis

Save the newly edited file, and try to visit your front-end again…it should no longer request the login. This is because PHP is an internal process, so it doesn’t require validation via htpassword, provided it uses server paths, as opposed to WP hooks or publically-accessible urls.

Hope this helps ??

I’m having this same problem…
On my ain .htaccess I added a FilesMatch rule to match wp-login.php only, and I secured the wp-admin directory, requiring a username and password to access it, using Password Protect directories in CPanel (basically adds what Grummel posted to the wp-admin directory’s .htaccess).
However, on the front end (there should be no requirement for normal visitors to the site to access wp-admin directory, nor wp-login.php page) if this plugin is enabled users are asked to log in. If the plugin is disabled, they are NOT asked.

How can we make this work????