Support

Home Forums Event Espresso Premium Error code: Invalid arguments supplied for the EE_Front_Controller class

Error code: Invalid arguments supplied for the EE_Front_Controller class

Posted: August 7, 2024 at 1:25 pm

Viewing 4 reply threads


Cgonzalez1

August 7, 2024 at 1:25 pm

You’ve reset my license key after I migrated a staging site to it’s permanent home. Since then, I’ve been unable to add shortcodes to some pages. I’m getting the error message: Invalid arguments supplied for the EE_Front_Controller class, 3 were required but 0 were passed.
This pops up on the left bottom of the page under the editor.
I was attempting to add the string [ESPRESSO_EVENTS category_slug=brainspotting-training-events table_search=false category_filter=false] which works on another page with a different category slug.


Tony

  • Support Staff

August 7, 2024 at 2:16 pm

Hi there,

The above error isn’t related to your license key.

How was the site migrated over?

Is the live site an exact copy of what you had running on staging?

Do you ave a full stack trace showing the error? (Usually that would be saved in the server error logs when the above error is thrown)


Cgonzalez1

August 13, 2024 at 10:27 am

Thank you for your support. I’ll find the error logs and get back to you once I’ve resolved the repeating problem of not being able to hold the support license key on the site.


Cgonzalez1

August 13, 2024 at 10:32 am

Your question about site migration makes me wonder if the two issues aren’t related.
I’m hosting on Siteground and used their “Staging Site” tools. When I was ready to go live with the site, I was unable to get the URL registrar to change the nameservers, so Siteground support talked me through changing the DNS records to point the site to the WordPress installation.
Then they talked me through changing the site URL using two tools, one was a Staging Site tool and the other was “Find and Replace” for those pages, links, and media that had not resolved.
Lastly, I used my broken link plugin to find 4 little outliers that need the URL changed.
This was the first time I’d used a Staging Site and the entire process seems as though it could be behind the problem.
Could you comment on this?


Tony

  • Support Staff

August 14, 2024 at 6:12 am

Your question about site migration makes me wonder if the two issues aren’t related.

Sorry, but I don’t follow.

Did the issue happen before the migration or only after the migration? If it only started happening directly after the migration then its likely related to how the site was migrated.

How… I can’t say currently but if the site is working as expected before X happened and then as soon as X is complete you get issue Y, something in X likely caused Y, right?

So the main question here is did adding shortcodes to the page work before the migration? Any other changes made after the migration?

I’m hosting on Siteground and used their “Staging Site” tools. When I was ready to go live with the site, I was unable to get the URL registrar to change the nameservers, so Siteground support talked me through changing the DNS records to point the site to the WordPress installation.

That’s all fine, your DNS changes won’t cause any of this (I’m not suggesting you said it was, just working through the points raised).

Then they talked me through changing the site URL using two tools, one was a Staging Site tool and the other was “Find and Replace” for those pages, links, and media that had not resolved.

Ok… but I’d have thought their migration tool would have done all of that.

Lastly, I used my broken link plugin to find 4 little outliers that need the URL changed.

The migration tool AND Find & Replace didn’t manage to fix all of the instances to the old URLs? That doesn’t seem right. 3 Plugins needed to update the DB just seems excessive to me, they are all essentially doing the same thing, finding X URL in the DB and replacing it with Y (that’s over simple, there’s more than just finding some text and replacing it going on here, but the idea is the same)… so why 3?

This was the first time I’d used a Staging Site and the entire process seems as though it could be behind the problem.
Could you comment on this?

So… possibly but every site is different so it’s hard to say. Even if I created a site and installed all of the same plugins you use I may not have the exact same config and could set up my pages using a different method to you etc and all of those small details matter with migrations.

—-

Let’s troubleshoot this as a ‘normal’ site for a second and work from there.

I can see you’re using 5.0.21.p which at the time was the latest version but its now 5.0.22.p, can you update to the latest version and check if you still have the same issue?

Your using Elementor, so how are you adding the above shortcode to the page?

Have you updated Elementor recently?

IIRC Siteground allows you to create a staging copy from your current live site, can you do that and check if the same issue happens on the staging site? (To troubleshoot this we are likely going to need to add some code to the site to see what is happening on the request so the if its reproducable on the staging site we can work there away from your sites visitors).

(Side note – do not do anything with your license key for testing this, your license key is NOT causing any of these issues. If you get a notice about it being used on multiple domains just ignore it for now, it won’t change any functionality and just needs us (me) to reset your key once we are done troubleshooting this)

Viewing 4 reply threads

The support post ‘Error code: Invalid arguments supplied for the EE_Front_Controller class’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Event Espresso