[scott6840]

I am getting the following php errors when I try to create a Nirvana child theme:

( ! ) Notice: Use of undefined constant WPLANG – assumed ‘WPLANG’ in C:\wamp64\www\FBCTestsite.net\wp-content\plugins\sermon-browser\sermon.php on line 188
Call Stack
#TimeMemoryFunctionLocation
10.0004240952{main}( )…\index.php:0
20.0007244104require( ‘C:\wamp64\www\FBCTestsite.net\wp-blog-header.php’ )…\index.php:17
30.0010264656require_once( ‘C:\wamp64\www\FBCTestsite.net\wp-load.php’ )…\wp-blog-header.php:13
40.0013275648require_once( ‘C:\wamp64\www\FBCTestsite.net\wp-config.php’ )…\wp-load.php:39
50.0022407456require_once( ‘C:\wamp64\www\FBCTestsite.net\wp-settings.php’ )…\wp-config.php:163
60.199325119120do_action( )…\wp-settings.php:411
70.232326571160call_user_func_array:{C:\wamp64\www\FBCTestsite.net\wp-includes\plugin.php:524}
( )…\plugin.php:524
80.232326571840sb_sermon_init( )…\plugin.php:524

This has only occurred since I upgraded to WP 4.6 and it doesn’t seem to affect the actual child theme generated but I haven’t yet done much of anything but create the child. I love the Nirvana theme but I don’t want to put a great deal of time into something that will no execute properly.

As you can see, I’m developing this on a WAMP64 localhost. Any ideas as to what would cause these errors and/or how to fix them?

Thanks for you time and input.

[Zed]

Is the sermon-browser plugin related to the child theme? as it is the one causing the issue:

( ! ) Notice: Use of undefined constant WPLANG – assumed ‘WPLANG’ in C:\wamp64\www\FBCTestsite.net\wp-content\plugins\sermon-browser\sermon.php on line 188

This tells you that the plugin relies on a (now deprecated) WordPress constant WPLANG, which is no longer used (since around 4.4 I think).
Either contact the author to update the plugin or try to manually add that constant (with the right value) in your wp-config.php file to see if it helps – other issues may remain, though, if the plugin was written for an older WordPress.

---

If you like our creations, help us share by rating them on WordPress.org.
Please check the available documentation and search the forums before starting a topic.

[scott6840]

Thanks for the reply.

I commented out the two offending lines of code:

// if (WPLANG != ”)
// setlocale(LC_ALL, WPLANG.’.UTF-8′);

and all is now good with the child theme.

There doesn’t seem to be a problem with the plug-in so I/m thinking that this is just some left-over code from earlier versions. The strange thing is that there was no problem with it under WP 4.5.7; It jumped up when I upgraded to 4.6.

Thanks again for your help.

[Author]

Posts