wpaart

Hi Phil

The ‘wp –info’ command should work from anywhere on your server.
The WordPress specific commands should be executed from within a WordPress directory.

Are there any specific error messages?

kind regards

Hi Rosario

The Google Support Website offers an in-depth explanation on publishing and embedding Google Documents. It seems to possible to restrict the embedded view to a range cells (e.g. range=A1:B14 ).

Glad to hear you got things working again.

Hi voidingnixx

I just tried out your original code in a test environment. It worked as it redirected to an url like this: https://www.websitehere.com/dir/jones4sesamystreet159870417

Maybe the ‘websitehere.com’ server has some rules in place that make that interfere with your redirection.

Have you tried to paste a redirect url in your browser like https://www.websitehere.com/dir/jones4sesamystreet159870417 that you know to work?

Hi voidingnixx

It looks like there is something wrong with the expansion of the variables inside the double quotes of the header string.

You could try adding and concatenating the variables one by one like this.

header( 'Location:https://www.websitehere.com/dir/' . $lname . $snumber . $sname . $zcode . $month . $year . $session )

kind regards

Just like XAMPP WAMP is not suited for production purposes.

The WordPress Codex has an article on installing WordPress on Microsoft IIS, maybe this can help you install WordPress securely on a Windows server.

kind regards

Hi gct7

XAMPP is not meant for production use but only for development environments. XAMPP is configured to be as open as possible to allow the developer anything he/she wants. For development environments, this is great but in a production environment, it could be fatal.

Please review the Windows FAQ on the XAMPP website.

kind regards

Hi shonev

The plugin.php file is part of the WordPress core used to process all the installed plugins. Although the error is reported in the plugin.php file it is probably caused by one of your plugins.

You could try to find the culprit by enabling your plugins one by one.

kind regards

Hi shonev

If you have FTP access you can disable a plugin by renaming the pluginfolder.

Hi

To rebuild your permalinks go to Settings > Permalinks, and click save changes.

Hi

It looks like the plugin ‘statpress’ has problems connecting to the database. You could try to access the admin area of your website to disable this plugin.

Hi

It is quite probable the error is caused by the theme you installed. In the tags to this post you included ‘Avada Theme’. The Avada website has a whole page about the ‘5OO internal server error‘.

Please post your Avada theme specific questions in the Avada support forums.

Hi

If you got FTP access you can locate the wordfence plugin folder and rename to something like wordfence_old. This will disable the plugin.

You could also remove the wordfence folder in its entirety and reinstall the plugin.

In this similar StackExchange question wp-cli maintainer Daniel Bachhuber suggests wrapping your statement within a class_exists() check. So that the command is only registered when WP-CLI class is available when WP-CLI is running.

if ( class_exists( 'WP_CLI' ) ) {
    WP_CLI::add_command( 'twelve', 'Twelve_Command' );
}

Maybe this plugin that removes the automatic pagination feature used for posts consisting of multiple pages can help you to enable the numeric slugs. https://www.ads-software.com/plugins/allow-numeric-stubs/