|
JuiceC
|
October 24, 2014 at 5:01 am
Hi,
I have tried installing the espresso decaf to a wordpress and it completely bricks the entire website! Everything just goes white, Frontend, backend, everything! I have to delete the plugin folder manually to get the website working again.
I was using 3.9.2, didnt work
Upgraded to 4.0, still doesn’t work
It doesn’t fill me with confidence to purchase this plug which is a shame as it is PERFECT for my needs, if it works…
Is there any known conflicts or has anyone else has this issue?
Many thanks
Ben
|
|
JuiceC
|
October 24, 2014 at 5:08 am
I found the issue for this but I thought I would still post my original issue for others that may have the same problem!
You need to make sure you have enough memory available. I added the following line into the wp-config.php file
define( 'WP_MEMORY_LIMIT', '64M' );
Hope that helps anyone that is having the same issue!
|
|
Tony
|
October 24, 2014 at 5:22 am
Hi Ben,
The white screen is known as WSOD (White Screen of Death)within the WordPress community and can be caused by many issues.
To find the cause of these you need to enable WP_Debug on the site, the whitescreen will then display the error that is causing causing it rather than just a whitescreen.
To enable WP_Debug you need to edit you wp-config.php file and add:
define( 'WP_DEBUG', true );
above the line that says
/* That’s all, stop editing! Happy blogging. */
So if you enable WP_debug, then enable Event Espresso, you will then see an error message. If you can paste that message here we can troubleshoot further.
We usually see this caused by shared hosting using rather low memory limits, but we can confirm this with the error message and advise on how to fix.
|
|
Tony
|
October 24, 2014 at 5:26 am
Hi Ben,
I see you have resolved the issue.
Just to note, I would still up that limit a little further, I’m guessing your host used the default 40MB WordPress sets by default, which EE took you over.
64MB will work (as it has done) although personally I always set ’96M’ just for some extra room. The more you ask of the server, the more RAM you use, so the extra will only help. So instead of:
define( 'WP_MEMORY_LIMIT', '64M' );
Just use
define( 'WP_MEMORY_LIMIT', '96M' );
|
|
JuiceC
|
October 24, 2014 at 5:34 am
Hi Tony,
Thanks for the reply. I will up that now!
Does the decaf version not allow pricing to be set? I get the option in the test drive but not when I installed decaf on my server.
Many thanks
Ben
|
|
Tony
|
October 24, 2014 at 6:34 am
Hi Ben,
This thread was marked resolved but I just wanted to check if you are you still having issues setting pricing for on your tickets when using Decaf?
If so can you provide some details of the steps taken and what happens?
|
|
JuiceC
|
October 24, 2014 at 7:11 am
Hi Tony,
Yes I am at the moment. The pricing option does not appear in the left hand menu like it does when I use your demo. I assume it is because it is a cut down version of it?
If you could confirm that all the options in your demo site are available in the EE4 without purchasing add-ons and I will purchase it straight away as I need to get a move on with the website.
Many thanks
Ben
|
|
Tony
|
October 24, 2014 at 7:54 am
None of the EE4 Add-on’s should effect the pricing section either way.
Did you use testdrive.eventespresso.com (EE3) or demoee.org (EE4) to demo Event Espresso?
Would it be possible for you to post a screenshot of the problem? (I recommeding using Monosnap)
-
This reply was modified 10 years, 1 month ago by
 Tony. Reason: None of the EE4 Add-ons*
|
|
JuiceC
|
October 24, 2014 at 9:20 am
Hi Tony,
The options are different in your demo to when I install it on my server. Please see the attached screenshot. The LEFT is my install and the RIGHT is your demoee.org
Why are they different?
Many thanks
Ben
|
|
Tony
|
October 24, 2014 at 9:54 am
Thank you, I understand now.
In that case I can say, this is not due to needing to buy extra Add-ons.
Decaf does not include the Pricing section so will not be displayed on your local version. It is on demoee.org as it does not use decaf.
However, some features we prevent the user from editing on demoee.org due to the fact that multiple users have access to the demo site at any one time. For example, say we left the message templates editable, User A modifies the default template to suit and logs out of demoee, users B, C, & D are now all using User A message template, which they will not be expecting.
We regularly reset the demo site, however in between the resets it would cause more confusion for those users, so we chose to remove options that would do that. Does that make sense?
Here is an example of EE4.4.3 Regular with no Add-on installed on one of my test sites – http://take.ms/Ip6tB
|
|
JuiceC
|
October 24, 2014 at 9:58 am
Hi Tony,
Excellent, thank you! That does make sense. I will purchase the plugin on Monday and start working with it!
Many thanks
Ben
|
|
Tony
|
October 24, 2014 at 10:16 am
No problem at all Ben and apologies for the confusion 🙂
If you do have further questions just let us know, have a great day!
|
