|
kim farmer
|
May 22, 2020 at 10:33 am
How can we change a setting so that other events don’t show on the event page that is being viewed? Right now its showing other events toward the bottom of the registration page.
|
|
kim farmer
|
May 22, 2020 at 10:34 am
Thank you for any help.
|
|
Tony
|
May 22, 2020 at 10:55 am
Hi there,
I’m not sure I follow, can you link me to a page that shows the problem?
Or a screenshot highlighting the additional events?
https://eventespresso.com/wiki/troubleshooting-checklist/#screenshots
|
|
kim farmer
|
May 22, 2020 at 10:57 am
here’s a link to the page. you can see the other events shown toward the bottom
http://milehighfitness.com/e/events/merrill-ms-online-yoga-may-june-2020/
|
|
Tony
|
May 22, 2020 at 11:16 am
Thank you, I understand now.
Those are actually from your theme and the simplest method to remove them is to hide them using some CSS:
.single-espresso_events .post-navigation {
display: none;
}
Add that to Dashboard -> Appearance -> Customize -> Additional CSS.
|
|
kim farmer
|
May 22, 2020 at 11:38 am
Ok thanks I’ll give it a shot!
|
|
kim farmer
|
May 22, 2020 at 11:57 am
can i also use ->appearance ->editor? for some reason ->customize won’t load in two different browsers but editor will.
|
|
Tony
|
May 22, 2020 at 1:51 pm
You could, but I don’t advise doing so.
You would be better adding a plugin like Simple Custom CSS and then adding the CSS to that.
|
|
kim farmer
|
May 22, 2020 at 5:43 pm
actually ->appearance -> widgets won’t load. ->appearance -> background won’t load
->appearance -> customize won’t load ->appearance -> customize won’t load. Tried in 2 different browsers. tried re-starting app as well.
|
|
kim farmer
|
May 23, 2020 at 7:35 am
can anyone think of any reason why those items won’t load? ideas?
|
|
kim farmer
|
May 23, 2020 at 7:36 am
again, tried in 2 different browsers, FF and chrome. I need to make changes and can’t
|
|
kim farmer
|
May 23, 2020 at 12:05 pm
hello can anyone help
|
|
kim farmer
|
May 23, 2020 at 12:28 pm
i tried on 2 different computers, same result, not loading
|
|
Tony
|
May 25, 2020 at 4:43 am
Hi there,
Support staff are available Monday – Friday: 7AM – 7PM EST (12PM – 12AM UTC) so you usually will not get a reply over the weekend.
Event Espresso generally doesn’t load on the pages you’ve mentioned (with the exception of widgets as we do load widgets) but there are multiple reasons for those not to load.
When you say they don’t load, what happens? White screen?
It sounds like there is a fatal error being thrown on the server and to fix that you’ll need to know the error being thrown. If you check your host’s control panel they will usually have a section to view any errors thrown by your site.
If you try to load one of the above pages and then load the error logs, search for ‘fatal errors’, do you see any?
|
|
kim farmer
|
May 25, 2020 at 6:44 am
yes they are loading blank white pages. My backend file hierarchy shows ‘wp-admin’, ‘wp-content’ and ‘wp-includes’ with subfolders. which subfolder will i find error logs?
|
|
kim farmer
|
May 25, 2020 at 6:46 am
I see a main folder called ‘logs’ in the main directory but nothing there that shows any error logs from event espresso
|
|
Tony
|
May 25, 2020 at 7:20 am
My backend file hierarchy shows ‘wp-admin’, ‘wp-content’ and ‘wp-includes’ with subfolders. which subfolder will i find error logs?
It depends on how the server is set up.
Usually, there is an error_log or error.log file in root but your host may have set it up differently to store errors in another location.
I see a main folder called ‘logs’ in the main directory but nothing there that shows any error logs from event espresso
You’re not looking for error logs from Event Espresso, your looking for the server PHP error logs, any error shutdown on your site (with a widescreen you’ll be getting a fatal error, which should be logged). I don’t think the error is from Event Espresso and we don’t add error logs.
If you can’t find the logs on the server, you can add this to your wp-config.php file:
https://eventespresso.com/wiki/troubleshooting-checklist/#wpdebug
You will usually already have define( 'WP_DEBUG', false ); in that file, the above snippet replaces that single line and tells your site to store any errors in /wp-content/debug.log
So after you’ve added that code go to the widgets page again to trigger the error and check the above file.
|
|
kim farmer
|
May 25, 2020 at 8:10 am
I called and they told me this is the error message from today.
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
|
|
kim farmer
|
May 25, 2020 at 8:10 am
does that mean anything to you?
|
|
Tony
|
May 25, 2020 at 8:32 am
May I ask, who is your host?
That’s not an error message, it’s the contents of .htaccess and not what you need.
|
|
kim farmer
|
May 25, 2020 at 1:40 pm
hmmmm ok
FX Domains
|
|
kim farmer
|
May 25, 2020 at 1:47 pm
there is a file called error_log that has a bunch of stuff in it. this particular line is there a million times I think:
[25-May-2020 19:42:38 UTC] PHP Warning: Use of undefined constant REQUEST_URI – assumed ‘REQUEST_URI’ (this will throw an Error in a future version of PHP) in /home/zs7l00lhxaxv/public_html/wp-content/themes/dt-the7-child/functions.php on line 73
|
|
kim farmer
|
May 25, 2020 at 1:47 pm
and this line is there alot too: [25-May-2020 19:41:05 UTC] PHP Warning: Use of undefined constant REQUEST_URI – assumed ‘REQUEST_URI’ (this will throw an Error in a future version of PHP) in /home/zs7l00lhxaxv/public_html/wp-content/themes/dt-the7/functions.php on line 73
|
|
Tony
|
May 26, 2020 at 3:05 am
That’s a PHP warning, it wouldn’t cause a white screen.
Search the file for ‘Fatal Error’, what comes up?
|
|
kim farmer
|
May 26, 2020 at 6:03 am
earlier you said this ‘You’re not looking for error logs from Event Espresso, your looking for the server PHP error logs’. so I thought you said I was looking for PHP errors? I searched for ‘fatal’ and the word was not found.
|
|
kim farmer
|
May 26, 2020 at 6:08 am
i went ahead replaced this
define( ‘WP_DEBUG’, false );
with this
https://eventespresso.com/wiki/troubleshooting-checklist/#wpdebug
but where is the wp-content/debug_log file?
its not in the main wp-content folder or e/wp-content folder.
|
|
Tony
|
May 26, 2020 at 2:58 pm
earlier you said this
To clarify, in your previous reply I thought you were asking for an error log file generated by Event Espresso itself, we don’t create our own error log, but any errors should be within the PHP Error log.
but where is the wp-content/debug_log file?
Wherever your WordPress directory is set up to go, on your site that sound like /e/wp-content/debug.log
Can I take a look at the site? Might be quicker that way.
I’ll need all of the requested details on this form:
https://eventespresso.com/send-login-details/
|
|
kim farmer
|
May 26, 2020 at 4:11 pm
do you need login details to EE or to my backend on FX domains?
|
|
Tony
|
May 26, 2020 at 4:36 pm
I need access to the site itself and access to files on the server, not your EE details.
I’m not superficially asking for your FX credentials as an FTP account is fine but if that is what you prefer to send over I’ll use them.
|
|
kim farmer
|
May 27, 2020 at 1:07 pm
hello did you get the login info?
|
|
Tony
|
May 27, 2020 at 4:26 pm
I did thank you.
When I try to log in with your host is asked for a one time passcode which has been sent to your email address, can you post that please.
|
|
kim farmer
|
May 27, 2020 at 4:49 pm
This reply has been marked as private.
|
|
Tony
|
May 28, 2020 at 4:21 am
Hi Kim,
I’ve replied via email as I think I missed the timeframe to use the code and it’s now requesting another.
If you prefer to follow up directly to the email I sent a little earlier that’s fine, just letting you know in case you are monitoring the forums over email.
|
|
kim farmer
|
May 28, 2020 at 5:12 am
This reply has been marked as private.
|
|
Tony
|
May 28, 2020 at 8:58 am
Just noting here that we will follow this up via email.
|
