threadi

Oh, I never though of XMLRPC, I just changed those default links.

What exactly do you mean by that? Renaming the xmlrpc.php file isn’t a viable solution, since the file is recreated after every WordPress update.

The Waveme theme is a commercial product, so we can’t assist you with it here in the forum. If you have any questions about it, please contact their support team: https://themeforest.net/item/waveme-music-platform-wordpress-theme/29428486/support

Okay, now we have some context for your issue.

But no, there’s no plugin for that. As you described above, you have to configure it manually. Since what you wrote seems to be a quote, I suspect you’re not entirely sure what you need to do?

Since I don’t do this often either, I just tested it myself. It’s actually two steps:

1) You need to add these entries to your Apache virtual host configuration:

SetEnv DB_NAME "my_database_name"
SetEnv DB_USER "my_user"
SetEnv DB_PASSWORD "my_secure_password"
SetEnv WP_ENVIRONMENT_TYPE "development"

2) In wp-config.php, you need to adjust this (don’t add anything! The constants are already there):

define( 'DB_NAME', getenv('DB_NAME') );
define( 'DB_USER', getenv('DB_USER') );
define( 'DB_PASSWORD', getenv('DB_PASSWORD') );

If, for example, the current entry is:

define( 'DB_NAME', 'my_database_name' );

you need to replace the value with the value of the variable, like this:

define( 'DB_NAME', getenv('DB_NAME') );

This worked perfectly on my test system.

If you don’t have virtual host configurations in Apache, you need to enter the information in the central configuration file. The name of this file depends on the server structure.

If you’re using a tool like cPanel, Plesk, ispconfig, or similar for server administration, you may need to enter the information elsewhere in that tool. The support documentation or manual for these tools will help you with this.

If you’re using an nginx server instead of Apache, a completely different configuration would be needed for step 1. The nginx manual should help with this.

Who are “they”? What requirements are you going by here?

I totally get what you mean. It always annoys me, too, when I install a new plugin and can’t immediately figure out where it’s located or how to use it.

But there are so many different plugins that, unfortunately, there’s no single place to find documentation on this. That’s why there aren’t any guidelines for plugin developers either. Many developers include instructions on their plugin page – sometimes as a video, sometimes as text, or even with screenshots.

Imagine you install a plugin that simply adds a block to the Block Editor. You don’t need anything at all in the backend for that. You just need to know that you can use it in the Block Editor.

Or a plugin that merely serves as a tool to hide those annoying admin notices. That doesn’t necessarily need a menu item in the backend either. It should just do what it promises.

You can see that this is a very complex issue. I totally understand your problem, but I don’t see a possible solution for it. If you come up with one that truly covers all possibilities, feel free to share your thoughts on Core Trac: https://core.trac.ww.wp.xz.cn/newticket

By the way: I intentionally build my own plugins to be as self-explanatory as possible. A clearly visible message after activation or a short guide makes getting started much easier. But unfortunately, not every developer thinks that far ahead 😐

Your slider is powered by a plugin called “Flo Flex Builder”. It appears to be part of the commercial theme you’re using, Velvet. The plugin’s developer discontinued the service in 2023: https://flothemes.com/ – they even warn against continued use on their blog, as there will be no further updates or support for it.

Unfortunately, we can’t help you with questions about this here in the forum either. No one here has access to the source code of the commercial theme you’re using. You really only have two options:

• Find someone who can look at your project with you in person. You can find someone like that here, for example: https://jobs.wordpress.net/
• Or pick out a new theme. Admittedly, the current one is really pretty. But you’ll face similar issues in the future. There are thousands of free ones that can look just as nice: https://ww.wp.xz.cn/themes/

You can add a new block at any time. Tap the plus sign at the top or the three dots on an existing block. This will let you add the block of your choice wherever you want.

No, the hook mentioned above simply suppresses the message. However, having so many autoload options isn’t an error in and of itself. There are hosting providers for which this isn’t a problem at all.

Furthermore, this cannot be the cause of the 500 error. The reason for the error should be visible in the error log. You can find it in your hosting area. If necessary, the support of your hosting can help you.

Alternatively, you could also enable debugging in WordPress. How to do this is described here: https://developer.ww.wp.xz.cn/advanced-administration/debug/debug-wordpress/ – also here the support of your hosting can help you if necessary to edit the file accordingly.

In both cases you should be able to see what the cause is in the logfile.

I would recommend that you report the issue on CoreTrac. In particular, you should include the post ID so that the issue can be reproduced if necessary: https://core.trac.ww.wp.xz.cn/newticket – this is the only way to actually fix the problem.