wpreser

Thanks, Peter!
Unfortunately I’m still on localhost, and with the problems I have, I’m afraid that I’ll never get it online!
But removing the post has nothing to do with local or online website, isn’t it?

My last reply here was deleted? !!!

Well, I see that all what was said in the link argue for making WordPress more secure!
If WordPress is a victim of its success, or because users don’t pay attention…etc., this is a strong reason to make WP more secure. One of these ignored methods is offering users to mislead hackers by renaming or hiding the working folders.
Doing such, WP security will be enhanced and its vulnerability will notably decrease.
At worst, offering such an option will not hurt! Instead, it will add a robust security layer and make it more trustworthy by users!
People will trust WP much more when they find it fulfilling their needs.

For this reason, there a lot of posts begging WP developers to make it easy to hide/rename WP folders (admin, content) but in vain, alas!

Yes I did but not so convinced by the arguments presented there, because they bypass an essential point in WP.
In WP installation, the plugins and wp-folders are known and listed in the source page! So, this is an opened door every kind of dangers!

Yes indeed, I’m talking about that topic. I’m sorry, I’ve to learn how the forum works to find my posts easily!
Thanks, anyway.
But sorry again, I’m not so convinced by the reasons presented on some links dealing with WP security.
So, my question/complain remains, even if the topic was closed :(!
What the arguments against renaming/hiding WP and plugins’ folders?
I think it would be in the interest of WP developers to make WP as attractive as possible. This attractiveness comes, in someway, from the easiness to configure and render WP the most secure possible.
When people find WP highly customizable and secure, they will switch to use it, wont’ they?

Hi,

In my case, I just downloaded the plugin and activated it WITHOUT adding any permalink; with the default setting the plugin adds the login extension to the URL end!
So, you may configured it with your URL and this doubled your URL!
Try to remove the plugin (delete its folder via your FTP if you haven’t access to your admin page) and re-install the plugin with the default setting to see if you get what you want.

Thanks John.
Yes, the database server is running.
I’m using WAMP.
It is a little bit strange that renaming the folder and then go back to the default name cause it not working!

The link you posted is interesting! It is stated that if we need to translate additional terms on the screen, we have to create a new .mo. This may solve my problem actually but I don’t know what to put in this new file: the translated terms that are not already translated or special codes to make the theme recognizable by the locale?
Do you have any idea?

Thank you

Thank you very much for your answer.
Actually, I’m not a developer, so I don’t know the “wonderful” potential of WordPress!
I’m using an already translated WP version, which is not fully supported by all themes. So, when I install some of them, there are some modifications to make. For example, in the interface I have to translate “search” field, or “posted on” …etc., to my locale because they are not automatically translated by my WP. When I translate them manually in the corresponding files (e.g “function.php”), I’m warned that all changes I made will be lost unless I register in UT8! So, to keep changes, I have to save the file in UT8 encoding. Doing so, the translated terms are recognized, but at the expense of some other problems.
Consequently, I’m wondering if WP PHP files were encoded as UT8 (not as ANSI), this may avoid such troubles and make WP more flexible, whatever the language or character being used.

Thank you, Marventus.

@ Richard, no I don’t have a backup! I just have the word doc where I copied/pasted them by caution.
@ fonglh, yes this is a good option when we don’t have a lot of posts.

Thank you, guys.

Regards,

Thanks Marventus.
The web host is also set up to localhost in the config file, so it is hard to make difference based on this feature, but the database name and username should differentiate the path.
Anyway, I removed the installation to re-start properly from scratch.
Thanks for the plugin link. It seems a cool one. Do you know if we can use it to re-name WP folders (wp-content, wp-admin, includes) for more security issue (security by obscurity, as pointed by WP developers)?

Cheers!

Thanks guys for your answers.
Actually, the error message I had came after installing other themes than from the default one. Sorry, I’ve deleted that theme to paste its file content here. So, the adminpanel belongs theme not to WP but to the theme I installed and deleted, so you are right.
However, my other question about UT8 coding still posed.
I would like to have php files in UT8 encoding to be able to add characters in other languages (internationalizing).
@s_ha_dum (was apljdi), yes the WP php files are in ANSI encoding, and this poses me many problems when I add some translated words or characters from other non-latin languages.
When I have to add a new character in another language, I’m prompted to change the encoding file format, and when I do so (when I register the php file in UT8) I have many error messages. So, my question is, if I change the encoding of all PHP files in WP from ANSI to UT8 encoding, will this work or will create other problems?
Thanks

Sorry, it is a WordPress error message, comes from WordPress installation. Otherwise, why I post it here?
About what few lines do you talk? I said that there was new few lines! I just wanted to login and I had this messge.
So, does this mean that we shouldn’t convert wp php files to ut8 enoding?