Problem upgrading from Php5.5 to Php7

I do not think there’s much code on my site, do you? The meteorite theme is suitable for transferring its own Customizer Panel settings to the customizer panel for the relevant codes. I think it would be right if the extra codes outside this and the extra codes to be added later are in the child-theme.

In the new site setup, I guess I do not need to use the “Customizer Export / Import” plugin after the child theme is created.

We can write the comment the way we want, right?
https://prntscr.com/jfc92o

I do not think there’s much code on my site, do you?

It should be fine. That’s why I said before that you should thake what’s more comfortable for you.

The meteorite theme is suitable for transferring its own Customizer Panel settings to the customizer panel for the relevant codes. I think it would be right if the extra codes outside this and the extra codes to be added later are in the child-theme.

I don’t really understand what you mean with this.

In the new site setup, I guess I do not need to use the “Customizer Export / Import” plugin after the child theme is created.

That plugin is only needed if you switch your theme to a child theme and want to have the same settings as you had before. Then you export once, switch theme to child theme and import them again. After that you can deactivate this.
So if you use a child theme from the beginning (I would suggest that you do so on every website where you know you will customize it) the plugin is not needed.

We can write the comment the way we want, right?
https://prntscr.com/jfc92o

Do you mean the comment we were talkin about before in the style.css of your child theme? The comment I mentioned is the following:

/*
Theme Name: Meteorite Child
Theme URI: https://terra-themes.com/theme/meteorite
Author: Terra Themes
Author URI: https://terra-themes.com
Version: 1.0
Template: meteorite
License: GNU General Public License v3 or later
License URI: https://www.gnu.org/licenses/gpl-3.0.html
Text Domain: meteorite
*/

This comment is important to be in every style.css because WordPress gets information about the theme from it.

In addition to this you can have as many comments as you want like you did.

No, the codes you already wrote must be absolutely. The “comment” I want to tell is the spelling (Turkish),

/ *
Kald?r?lan ana menü yaz? tipi boyutu ayar? (translate: Removed main menu font size setting)
* /

Removed code.

#main-nav > ul > li > a {
  font-size: 16px;
}

https://prnt.sc/jfc92o
Comments written in Turkish (Code to be set in the customizer, main menu code). I wrote it like this. I wrote it like this. It is not a problem right?

Sorry I can not describe it as I want with translate.

The “comment” I want to tell is the spelling (Turkish),

You can write what ever you want inside of the comment.

Do you still have any questions about this or can I mark this topic as resolved?

Of course… there will be one final question. In the sense of site security, removing wp_ prefix would be a problem, like hiding WordPress version information?

I am very surprised with your excellent support and interest, so thank you so much…

What do you mean with the wp_ prefix?

To hide the WordPress verion you can use this code. Feel free to remove it, it even improves the security.

// remove version from head
remove_action('wp_head', 'wp_generator');

Another small but good thing might be to delete the readme.txt files of your WordPress installation, because this file provides some information about the system too.

Yes, that’s what I mean wp_ prefix. To remove or modify.
https://prntscr.com/jfsh35
I am replacing “wp_ prefix” php with MyAdmin, but I can not change login.php “wp_ prefix”.

I added the code to the fonctiions.php file.
I deleted the readme.html, license.txt, and wp-sample-config.php files.

I have added the code to “Delete and disable previous WordPress text versions” in the config.php.

//disable WP Post Revisions
define('AUTOSAVE_INTERVAL', 300); // seconds
define('WP_POST_REVISIONS', false);

To remove or modify.
https://prntscr.com/jfsh35
I am replacing “wp_ prefix” php with MyAdmin, but I can not change login.php “wp_ prefix”.

Without further information I can’t tell you what’s wrong and why it doesn’t work. Why can’t you change the prefix inside of the file? Where are you looking for the prefix? Because it’s in wp-config.php and not (as you wrote) in something like login.php.

But as I researched a bit I found a blog post from a WordPress security plugin which tells that changing the prefix doesn’t increase the security. So it’s useless, because if an attacker gains access to your database through a SQL injection they can simply find the prefix. You can read on your own here: WordPress Table Preix: Changing it Does Nothing to Improve Security.

The rest you did should be fine.

The process I tested;
“wp-login.php” change the file name > replace all the names in the file with the newly named file.

As far as I understand, attacks are made with SQL injection attacks, the best solution to prevent this is the “WordPress Firewall” plugin. I can download and use it. This information was very useful, thank you..

How is the “WordPress Firewall” plugin success rate? Does it provide full security?

The process I tested;
“wp-login.php” change the file name > replace all the names in the file with the newly named file.

I haven’t really worked with a renamed wp-login.php file. Therefore I can’t really help you with this. But I’m sure there is further information out there you can find.

How is the “WordPress Firewall” plugin success rate? Does it provide full security?

I really cannot say anything about plugins from 3rd parties. I can only support you at questions related to Meteorite. This is a question for the plugins support forum, not mine.

I’ll mark this topic as resolved now. For the future please try to post every question about something new in a new topic. This one was originally about PHP 5.5. Then about child themes and security plugins after that. If another user has a question about the child theme setup he will never think about to find that answer inside of a PHP topic.

All right, thank you ..