Support

August 7, 2015 at 5:43 am

Are you modifying code (any code including text changes) within the plugins directory? Which is wp-content/plugins/event-espresso-core-reg/

You’ve mentioned its several files, so I can’t ask which file specifically. I’m trying to find out if this is caused by your modifications within core (if that’s where your are changing code)

So if you’ve modified core, then used the one click update, you would be running the ‘standard’ version of EE with no modifications and this should not be happening.

When you update a plugin what WordPress actually does is delete the current plugin, download the latest version and replace the plugin with that. If your modifying core and then use the standard once click updates you’ll lose all of the modified code because of the above.

This error:

“the requested route_register could not be mapped to any registered modules”.

Means that EE can not find the route for ‘route_register’, problem is there is no route for route_register because it shouldn’t be looking for that route in the first place (it will never exist)

Right now the only cause I can see for this is modified code within core that’s causing problems looking for ‘events’, I’ll check in with developers on troubleshooting steps for this. However due to time differences it will be a little before the respond.

• This reply was modified 9 years, 3 months ago by Tony.

August 7, 2015 at 6:20 am

What I don’t understand is, as mentioned above, if you’ve modified core then used one click updates you would no longer have a modified version of Event Espresso. Yet it seems you have?

So are you modifying code (any code including text changes) within the plugins directory? Which is wp-content/plugins/event-espresso-core-reg/ or another directory?

August 7, 2015 at 7:49 am

Ok, any files within the plugin directory is considered Event Espresso ‘core’ in the same way any modifications made to WordPress core files is considered to be any of the standard WP files.

The internal structure of the directories/files makes no difference, modifying /core/ or /modules/ is still modifying the core code for Event Espresso.

As you mentioned modules its likely that error is being caused by modifying:

event-espresso-core-reg\core\modules\event_single\EED_Event_Single.module.php

On line 46 you should have:

EE_Config::register_route( __( 'event', 'event_espresso' ), 'Event_Single', 'run' );

Is yours different? (You may have a slightly different line number), I’m guessing yours doesn’t have ‘Event_Single’ on that line but something else.

There is no way of doing that without modifying stuff in the “modules” folder.

Sure there is.

You want to move the ticket selector to the bottom of the content? You can use this gist:

https://gist.github.com/joshfeck/1151c89082ccb5c0b478

Add that to a Site Specific Plugin, it will hook in and place the ticket selector at the bottom of the single event page. No core modification needed.

You can get event more granular control using template files within your theme archive-espresso_events.php or single-espresso_events.php for example, this is much more involved (just those two templates are not enough) and is not usually necessary but is available if needed.

So I re-uploaded my modified file as I do not want to spend several hours wroking out how I managed to change it last year

Then your back to running a modified version of core. The problem here (especially if your replacing whole files from previous versions) is that any fixes or new code we’ve introduced within those files now isn’t included within your copy of Event Espresso, this could cause fatal errors within other sections of EE if for example we call a function that should exist but doesn’t (or even leave your site open to exploits if we’ve patched a hole).

Whilst it may seem like currently the only issue here is the error message, this is only going to get worse if you continue to modify core files this way and we can not provide support when this happens. Currently it may seem a hassle but the longer you replace files within core the more likely you are to running into deeper issues.

You will find that almost all requests to make changes to the output of EE can be done through hooks and/or template files if your confident with dealing with those. If you do find something that it appears you can not change just let us know, it is likely there is a way to do it and if not we can request a hook be added to allow it to be done.

August 7, 2015 at 10:43 am

Hi Robert,

I’ve just ran a registration on your site and didn’t see any errors on the checkout page, do you still see this?

I did notice ?ee=_register within the query string which would cause the error you mentioned, however I’m unsure where that is from.

August 7, 2015 at 11:50 am

Hi Rob,

I can weigh in on the unknown addresses. It doesn’t necessarily have to be an address outside of the US for that to happen. Can you let me know the address you’re having issues with?

August 7, 2015 at 2:43 pm

Hi Robert, on an earlier version of Event Espresso 4, there were success messages that appeared. Those no longer appear in the current version of Event Espresso 4 while a registration is taking place.

The only pop-ups that you should see are related to an error made by the registrant. For example, if they forgot to enter an option for a field, then they should see a popup that has help messaging to remind them to complete that field.

I do not recommend hiding this because the registrant may not immediately understand that they skipped a specific field (question) and they could think that the registration process isn’t working when it actually isn’t letting them proceed because a required field has not been completed.

—
Lorenzo

August 10, 2015 at 9:44 am

Hello Robert, that does not look familiar and I was able to find a couple reports from last year.

You mentioned that you overwrote the old files. Was this done via SFTP or FTP?

Event Espresso 4.7.x has a different folder structure than older versions like 4.4.x. If you overwrote the files and folders, then please deactivate and remove Event Espresso 4 from your WP dashboard.

Then download a new copy from your account page and upload the zip file and activate through the WP plugins screen in your WP dashboard.

Let us know if that helps with the issue.

Thanks

—
Lorenzo

August 11, 2015 at 9:28 am

Hi Robert,

We are trying to work out what could be causing this, it isn’t a common issue, nor a bug within Event Espresso. Event Espresso is doing what it should, looking for a route called _register which is being passed with the query string.

So can you confirm you have remove all modifications to Event Espresso? You have deleted Event Espresso from the plugins menu, downloaded a clean copy from your account page and installed that through the Dashboard as is?

I notice the single event page is showing the ticket selector at the bottom of the page, has that been done using the Gist I provided above or through another method?

Do you have any site specific plugins to add/change the checkout page? Or functions within your themes.php file to do the same?

If you switch to one of the default themes such as twentyfourteen and retest, does the same error message show?

August 12, 2015 at 5:59 am

You can switch themes for just admins using the Theme Test Drive plugin.

That allows you to enabled a theme within the admin and you can view your site using that theme but your visitors will continue to use the regular theme.

I can take a quick look at the template file and see if I can see anything obvious that is causing it, however can you please confirm if you have done the above steps to now run a ‘clean’ version of Event Espresso.

So can you confirm you have remove all modifications to Event Espresso? You have deleted Event Espresso from the plugins menu, downloaded a clean copy from your account page and installed that through the Dashboard as is?

Otherwise the template files could be leading us in completely the wrong direction if there are still modifications within core.

August 12, 2015 at 9:08 am

The easiest way is to host a zip file containing all of the templates and include a link here that I can use to download them.

You can add the files to the wp install through the Media Library on your site if your prefer, or use something like DropBox.

November 18, 2015 at 8:54 am

Hello again Robert,

As of Event Espresso 4.8.21, there is a custom display re-order option available in the WordPress dashboard.

Backup your WordPress and update your software

https://eventespresso.com/wiki/how-to-back-up-your-site/

You can see the change log for Event Espresso 4 here:

https://eventespresso.com/wiki/ee4-changelog/

Remove existing filters for adjusting the order

If you have used some of the suggested filters to adjust the order of your event elements, then you’ll want to first remove those from your website and they may have been added to your child theme’s functions.php file or a site specific plugin.

Set a custom order through the Templates screen

Afterwards, go to your WP dashboard (WP-admin) –> Event Espresso –> Events –> Templates. The Use Custom Display Order options in the Templates screen can be used to reorder the events elements on the single event page as well as the events listing page.

Again, be sure that any of the filters for adjusting the order have been removed from your site specific plugin or your child theme’s functions.php file before turning on the template reorder option. Otherwise, you may see duplicate content.

Thanks

—
Lorenzo