[Heather_G]

Oh right, so that article wasn’t really meant to be helpful in this case since I was clearly asking about wp-emembers.

Thanks for those specific hosting suggestions.

I did find threads about those two caching plugins, but they do need to be implemented if I move to a server that doesn’t apply forced caching? I tried to fix the error previously by adding WP Super Cache, but it didn’t help, I assume because the server was applying forced caching.

[Heather_G]

Interesting. So you recommend Bluehost under the heading, ‘Short List of Cheap and Good Web Hosting Companies’. However another section of the article states that you didn’t have a good experience with them but no details are listed. So I’m feeling a little confused…

Your article seems to say that shared hosting should be fine with your plugin… so any ideas why I’m having this issue then?

Thanks

[Heather_G]

For some reason the code you gave me wasn’t outputting anything. However I used the instructions I found here: https://www.wpwhitesecurity.com/absolute-path-webserver-php/

It outputted the following path: /home3/omsocorg/public_html/

I updated the path to: /home3/omsocorg/public_html/wp-content/themes/omsoc-child/lang/fr.php

But it still isn’t working.

Any ideas?

Thanks!

[Heather_G]

I see. It is more complicated than I realized. My PHP skills are pretty basic, but I’m always happy to learn more. We did have a developer working on the site, but he was so challenging to work with, we had to cease working with him. Now I’m just trying to polish things up as best I can before launch.

And speaking of launch, the server isn’t pointing to the actual domain yet, do I need to wait until it is pointed to try to find the path to the file?

Thanks again for your help.

[Heather_G]

Interesting. I tried your suggested path (it matches the structure of my WP installation) and it didn’t work. I also tried to remove each folder in order one-by-one starting from ‘home’ until I was down to /lang/fr.php but nothing worked. I call the hosting company (I’m using Bluehost and am on a shared server) and they said there was no restrictions on using a file URL, so the original URL I used should have worked. (I wasn’t aware of the security risk so that interesting to think about, but regardless, I’m just trying to get this to work for now).

Any other ideas as to why it wouldn’t be working? Is there a way to redefine the string directly in my child theme’s function file?

Thanks

[Heather_G]

I realized that it doesn’t make much difference since I’m currently on a test site. Here’s the code:

add_filter('emember_language_loading_override', 'load_my_custom_emember_language');

function load_my_custom_emember_language()

{

$language_file = "http://69.195.124.204/~omsocorg/wp-content/themes/omsoc-child/lang/fr.php";

include_once($language_file);

return "custom-file-loaded";

}

[Heather_G]

Sure. Can I reply privately?

Thanks

[Heather_G]

Sorry for the slow response. My client put the project on hold for awhile.

I installed the fresh copy but I’m getting the same error.

Thanks!

[Heather_G]

I just thought I would add that I found a solution to the postal code issue for those of us who are handing off projects and so re-uploading plugin files after an upgrade is not an option.

I added this to my child theme:

label[for=wp_emember_zipcode]::before {

content: "Postal Code: ";

font-size: 14px;

}

label[for=wp_emember_zipcode]  {

display: block;

font-size: 0px

}

[Author]

Posts