gurra

Hi,

I sure try. From the start I installed WordPress on the web server in the subdirectory “wordpress”. I made all the work with the site, e.g. installed plugins needed including aiowps and made all plugins settings, and of course put the content in place etc. In this situation a public visitor could only access to the site via the address mySiteAdress.se/wordpress.

Now, when finished the work I wanted the site to be accessible directly via the domain address, i.e. mySiteAdress.se, so without the ending “/wordpress”. I followed the instructions on WordPress.org – the page: https://wordpress.org/support/article/giving-wordpress-its-own-directory/ . The instructions include two main steps: to copy (not move) the index.php and .htaccess files residing in the wordpress directory and place these files/copies in the website root directory (and also for this context some more nonessential steps). What this in fact means is that after performing the steps there are two identical (nearly) .htaccess files on the web server – one in the website root directory and one in the wordpress directory. Consequently, from start both these files includes all the rules that comes from the settings made in the aiowps plugin.

I hope you now can understand my question which you quote: “If I make new settings in aiowps will these changes automatically be listed in the .htaccess file(s) they should be, I guess in both the .htaccess file in the wordpress directory and in the one in the root directory?”

As told earlier, my tests show that when now changing a setting in aiowps, this changes the rules listed in the .htaccess file in the website root directory, but not the rules in .htaccess file in the wordpress directory. So, the files will now differ. But if that is okey, all is okey.

Perhaps the answer to the question is so easy and obvious that the question is difficult to understand. But I did put it anyway because I have had several problems with the .htaccess files when changing the site url as described in the second paragraph above, and wanted to be sure all will work okey.

I hope you get it. The question can be summarized to: seems all works as it should now?

Hi,

Thanks for your answer.

I made a test. I changed a setting in aiowps in WP admin. The change affected the rules in the .htaccess file in the root directory, but not the rules in the .htaccess file in the wordpress directory (where all the WP files/installation resides – only the index.php and the .htaccess is copyed to the root). Is this what shall happen, i.e. what is correct and safe? If “yes”, then of course all is fine, and I can be sure all works correctly.

On the right side of the logo, on the top of the page http://www.malcare.com is written GDPR READY. That is what I am reffering to.

The most critical issue regarding GDPR is if personal information is transferred from EU to USA. Some security plugins do.

Regarding the last question: If MalCare doesn’t transfer personal information to USA, perhaps they do to servers in EU. If so an agreement between the MalCare company and the customer need to be setup. If no transferring at all no agreement is needed. Just good to know.

Thanks for quick reply!

Checking the theme readme.txt changelog, strengthen my suspicion the problem is caused by the last theme update. One of the changes is “Added Read More Option for Blog Page”. Seems directly connected to the problem on my site. Perhaps the developer missed to add a “language string” to this option. But at the same time some strange – I thought it was exactly this option I have used for a long time.

Well, also a somewhat strange that, as you say, themes own pot files sometimes can be corrupt. Anyway, in this case it worked when I used it when starting the site. But if something changed, I now also have tried the WP-translation. I downloaded it as a po file, made some changes, saved it as sv_SE.po file and consequently also as a mo file (using the Poedit app), and uploaded it to the server. Nothing happens/changes.

Interesting what you write about strings that are “context aware”. But I guess that this can’t be applied in this case as an explanation.

Well, my own created po file only includes two translated words, who are already translated in the in the WP translation, so it will hardly contribute to anything more. The changes I did in the WP translation, were only minor adjustments, matters of taste.

Hi @tobifjellner,

Thanks very much for your tip and information about WP translations. It’s a lot I didn’t know before, so the information is very welcome. I will check further if what you suggest is something for me to commit to, including the Swedish slack team.

Regarding this case, yes, the mo file is also in the correct/same folder as the po file. So, this shouldn’t be the problem. But there are two other things that confuses me slightly. In the po/mo file I used before the last theme update, I translated “More” to Swedish, and this worked fine on the blog page. But when “Read more” occurred on the blog page after the last theme update, I also translated this expression in the po/mo file. But nothing happened. Furthermore, the expression “Read more” is partly placed on different places in different po files (the one I used before last update of the theme, the one generated by the accesspress-lite.pot file which accompanies the theme, and the WP translation on https://translate.wordpress.org/projects/wp-themes/accesspress-lite/sv/default/ which you refer to), and the expression also occurs two times in the dot file. May some of these things have a connection to the problem?

Otherwise I wonder if something in the last update of the theme may have an impact on how the translations works? I guess this is a question primarily the theme creator will be able to answer.

Regards / Ha det gott!

Ok. Thanks for your answer. I do not use the plugin at the moment, but I might do later.