edit functions.php in backend

I can’t find the editor link in Woodmart child theme. Is like missing.
I’ve read your post: https://xtemos.com/forums/topic/theme-editor-missing-issues/
but in my wp-config.php there’s no code to disable.
Could you please help me with that? thanks

Hello,

If the Theme File Editor is missing and there’s no DISALLOW_FILE_EDIT constant in your wp-config.php

Please follow this complete guide and enable it: https://www.wpbeginner.com/wp-tutorials/how-to-fix-missing-theme-file-editor-in-wordpress-admin-easy-fix/

Best Regards,

hi,
the link that you provided suggest 3 kind of solution.
1) the theme editor button has changed position. Should be under Tools but it’s not (please have a look to attached screenshot)
2) a security plugin locks this feature. The only security plugin I use is Wordfence Security that does’t have this kind of block and in any case i tried deactivating it with any good news
3) wp-config.php contain script that block the feature. I can’t find the suggested code. I’ve pasted here the file code.
Do you have any other suggestion to solve the issue?
Thanks a lot.

<?php
define( ‘SBI_ENCRYPTION_KEY’, ‘tdDMp&MVQpLs^5OgptDzEz**h8aBFGQmxt5SPPg()t$Wvv&chKH%*6OupHWSb6n$’ );

define( ‘SBI_ENCRYPTION_SALT’, ‘ijy6R$BRkVJV(4sKHy5rW*kJSXfFwA2HmuUvMK*B25oWacKCA^kmXO^YmQ90nrkL’ );

define( ‘WP_CACHE’, true );

// Added by WP Rocket

// Added by WP Rocket
// Added by WP Rocket
if ( !headers_sent() ) {
ob_start();
}

/**

* The base configuration for WordPress

*

* The wp-config.php creation script uses this file during the installation.

* You don’t have to use the web site, you can copy this file to “wp-config.php”

* and fill in the values.

*

* This file contains the following configurations:

*

* * Database settings

* * Secret keys

* * Database table prefix

* * ABSPATH

*

* @link https://wordpress.org/documentation/article/editing-wp-config-php/

*

* @package WordPress

*/

// ** Database settings – You can get this info from your web host ** //

/** The name of the database for WordPress */

define( ‘DB_NAME’, ‘nrttst123qwe_nrt526544’ );

/** Database username */

define( ‘DB_USER’, ‘nrttst123qwe_nrt526544’ );

/** Database password */

define( ‘DB_PASSWORD’, ‘HPpt66WfR6v4n’ );

/** Database hostname */

define( ‘DB_HOST’, ‘localhost’ );

/** Database charset to use in creating database tables. */

define( ‘DB_CHARSET’, ‘utf8’ );

/** The database collate type. Don’t change this if in doubt. */

define( ‘DB_COLLATE’, ” );

/**#@+

* Authentication unique keys and salts.

*

* Change these to different unique phrases! You can generate these using

* the {@link https://api.wordpress.org/secret-key/1.1/salt/ WordPress.org secret-key service}.

*

* You can change these at any point in time to invalidate all existing cookies.

* This will force all users to have to log in again.

*

* @since 2.6.0

*/

define( ‘AUTH_KEY’, ‘*On fLj&W[fNGQX,zRk:& @SNr-D>on~bqOJ;xA8oUxl:;0xv(jjf[$)N7K~dKQ6’ );

define( ‘SECURE_AUTH_KEY’, ’40:{SkVD5>?O44n.M-!#8!~}Fl}]okKn-k#YhvCCx_mPg<~<uD<luMwvE9kR+6)F’ );

define( ‘LOGGED_IN_KEY’, ‘WZ?2%#/?7P1zDtXnb9.B)EzG,qJCUd33?c$]9JDP6XhA_!$0-Ji5w?<={QV7_&!W’ );

define( ‘NONCE_KEY’, ‘7JpB@em>~qKG34m&hTF&~d+]ac87f{.#!ib@2hoaGW$T[#LyE%7X&.Ee2hX FvyO’ );

define( ‘AUTH_SALT’, ‘b5j=o 0GdZ^uIdf:A>=f>N1~.cV::EfOK3AniFm-EDmAht3IFOacvU61 ^hTY5′ );

define( ‘SECURE_AUTH_SALT’, ‘uxZ7.c$o7>}0UKTE=VglDX}|$Ck;R(;yOgf^3vTEm<eGQ%?NJ73(q1)UW(Y^Yba}’ );

define( ‘LOGGED_IN_SALT’, ’58q,q;}bMR2k_e/fX7D/24x3w6`g*^+2ty/L37(Ad;Ov9CJ<<xzT#65^m|lz>k1K’ );

define( ‘NONCE_SALT’, ‘KjN;ES/L3tn2K(JRbWi|l<]8zEA16ueiSqy#]oSU=bi25X~yDwLJ108rRLAe^4x%’ );

/**#@-*/

/**

* WordPress database table prefix.

*

* You can have multiple installations in one database if you give each

* a unique prefix. Only numbers, letters, and underscores please!

*/

$table_prefix = ‘wp_’;

/**

* For developers: WordPress debugging mode.

*

* Change this to true to enable the display of notices during development.

* It is strongly recommended that plugin and theme developers use WP_DEBUG

* in their development environments.

*

* For information on other constants that can be used for debugging,

* visit the documentation.

*

* @link https://wordpress.org/documentation/article/debugging-in-wordpress/

*/

define( ‘WP_DEBUG’, false );

define(‘WP_MEMORY_LIMIT’, ‘512M’);
define(‘WP_MAX_MEMORY_LIMIT’, ‘512M’);

/* Add any custom values between this line and the “stop editing” line. */

/* That’s all, stop editing! Happy publishing. */

/** Absolute path to the WordPress directory. */

if ( ! defined( ‘ABSPATH’ ) ) {

define( ‘ABSPATH’, __DIR__ . ‘/’ );

}

/** Sets up WordPress vars and included files. */

Attachments:

You must be logged in to view attached files.

Hello,

Sorry to hear about the inconvenience. Kindly, please share your Site WP-ADMIN Login details in the Private Content field so that we can check this concern on your Site and help you out accordingly.

Best Regards,

[Author]

Posts