Milos

Hi there,

Thank you for contacting us.

The “Hello Theme #1234” pattern strongly suggests that something is programmatically creating pages on every admin load using wp_insert_post(), most commonly through hooks like admin_init or init.

Since the issue stops when Elementor is deactivated and continues regardless of the active theme, that suggests Elementor itself, or something that runs only when Elementor is active, is triggering it.

The first thing I recommend is temporarily deactivating all plugins except Elementor. Then click around the WordPress admin again and see if the pages are still being created. If the issue stops, reactivate the other plugins one by one until it comes back. That will identify the exact plugin responsible. If this is a live site and you don’t want to affect visitors, you can use the Health Check & Troubleshooting plugin to run this test in isolation under your user session.

If the issue still happens with only Elementor active, I suggest performing a clean reinstall of Elementor. Deactivate and delete the plugin completely, then download a fresh copy and reinstall it.

Before doing that, you can also try rolling back to a previous version from Elementor → Tools → Version Control to see if the behavior changes. If a rollback resolves it, that points to a version-specific regression.

To pinpoint exactly what’s creating the pages, the most reliable method is logging the source of the wp_insert_post() call. You can temporarily enable WordPress debug logging in wp-config.php and add a small snippet that logs the backtrace whenever a page titled “Hello Theme #…” is created. Once reproduced, checking wp-content/debug.log will show the exact plugin file path responsible. That removes any guesswork and tells us precisely what component is generating the pages.

In most cases like this, the cause turns out to be an Elementor-related add-on, onboarding module, template importer, or demo content feature that misfires during admin load. Once we see the file path from the debug log, we’ll know exactly what needs to be adjusted or removed.

Thank you for your understanding.

Kind regards,

Hello there,

Thank you for being so patient.

We highly recommend that you report this issue to the support team for this theme, so they may further troubleshoot and provide any recommendation (or possible fix) to resolve this issue.

Should they need any help from us, they can open an issue on our Github account and our developers will be happy to assist. https://github.com/elementor/elementor/issues

Kind regards,

• This reply was modified 2 months, 1 week ago by Milos.

Hello there,

Yes, there is a huge possibility that something is lost when switching from one provider to another.

Also you can try following methods to resolve error 500 from your side:

• Increase the WP memory limit to match Elementor’s system requirements. Activate the debug mode of WordPress to check how many MB you need exactly. Contact your hosting provider for further assistance. For details, refer Debugging in WordPress.
• Decrease or clear the number of post revisions stored in the database. When there are too many revisions stored, the hosting memory may become exhausted, which can lead to this error. You can use the available plugins to resolve this issue. For example, WP Sweep. To use this plugin, watch https://www.youtube.com/watch?v=xt4U4e8NSIQ

Please backup you site before perform recomended actions.

I am looking forward to hearing back from you soon.

Kind regards,

Hi there,

Thanks for contacting us and hope you are doing well and having a great day.

To rule out the possibility of a plugin or theme conflict, please deactivate all your plugins (besides Elementor ). If it solves the issue reactivate them one by one to find the culprit. If it didn’t help, switch your theme (temporarily) to a default WP theme such as Twenty Nineteen and see if it makes any difference.

Also, this could happen due to our Elementor performance experiments you can try to deactivate them. To deactivate them you can go to Elementor > settings > features

Performance features currently in the experimental stage are:

• Element Caching – Elements caching reduces loading times by serving up a copy of an element instead of rendering it fresh every time the page is loaded. When active, Elementor will determine which elements can benefit from static loading – but you can override this.
• Inline Font Icons – This experiment renders icons as SVGs without loading the Font-Awesome and eicons libraries. Since SVGs are vector-based images which are rendered using the browser’s engine, they do not increase server requests which improves performance

I am looking forward to hearing back from you soon.

Kind regards,

HI there,

Can you share your page url where the gap is showing so we can inspect using Google Developer tools and see where the gap is comming from.

Thank you for your patience and understanding.

Kind regards,

Hello there,

Thank you for your patience!

Would it be possible for you to tell us more details about your issue, can you please provide us with a screencast demonstrating the issue?

This will be useful to us as we will better understand the issue you’re experiencing and provide you with better support.

I am looking forward to your reply!

Kind Regar

Hello there,

Thank you for your patience!

Would it be possible for you to tell us more details about your issue, can you please provide us with a screencast demonstrating the issue?

This will be useful to us as we will better understand the issue you’re experiencing and provide you with better support.

I am looking forward to your reply!

Kind Regards