Support

Home Forums Event Espresso Premium php.ini issue while migrating

php.ini issue while migrating

Posted: April 16, 2020 at 12:54 am


Khalid Joharji

April 16, 2020 at 12:54 am

Dear Support,

I wanted to upgarde my website php and to do so i had to purchase a new hosting plan from godaddy and transform my websites to it

the new plan is a managed wordpress. which has a migrate service in it.

all websites were migrated perfectly but the one with your plugin did not migrate. after communicating with support for to many days they asked me to disabled all plugins and i did but they told me there is still a php code running in php.ini

the following are the text in php.in i wanted to know if there is anything in the code related to the plugin? and if yes can you rewrite it to maintain the plug in working while its not very different from the original php.in so it can migrate without issues?

the code in the file is the following:

********************
register_globals = off
allow_url_fopen = off

expose_php = Off
max_input_time = 60
variables_order = “EGPCS”
extension_dir = ./
upload_tmp_dir = /tmp
precision = 12
SMTP = relay-hosting.secureserver.net
url_rewriter.tags = “a=href,area=href,frame=src,input=src,form=,fieldset=”

; Only uncomment zend optimizer lines if your application requires Zend Optimizer support

;[Zend]
;zend_optimizer.optimization_level=15
;zend_extension_manager.optimizer=/usr/local/Zend/lib/Optimizer-3.3.3
;zend_extension_manager.optimizer_ts=/usr/local/Zend/lib/Optimizer_TS-3.3.3
;zend_extension=/usr/local/Zend/lib/Optimizer-3.3.3/ZendExtensionManager.so
;zend_extension_ts=/usr/local/Zend/lib/Optimizer_TS-3.3.3/ZendExtensionManager_TS.so

; — Be very careful to not to disable a function which might be needed!
; — Uncomment the following lines to increase the security of your PHP site.

;disable_functions = “highlight_file,ini_alter,ini_restore,openlog,passthru,
; phpinfo, exec, system, dl, fsockopen, set_time_limit,
; popen, proc_open, proc_nice,shell_exec,show_source,symlink”

************************


Tony

  • Support Staff

April 16, 2020 at 4:46 am

Hi there,

I wanted to upgarde my website php and to do so i had to purchase a new hosting plan from godaddy and transform my websites to it

the new plan is a managed wordpress. which has a migrate service in it.

It’s great that you are updating the version of PHP you are using (I’m assuming PHP7?) but I should note here that we do NOT recommend GoDaddy Manager WordPress hosting for EE. That plan forces server side caching on all pages of your site and then when you request for it to be disabled (which you will be required to do for registrations to functions) then depending on which support operator you speak to, they’ll tell you its not possible, or it is! (meaning you’ll get conflicting answers).

I’ve posted about this many times in multiple threads so rather than retype it out, I’ll like to another that gives details on the problem here:

https://eventespresso.com/topic/cart-is-showing-no-tickets-selected-and-says-no-event-selected/#post-285753

They may have changed things since that last post, but its still not a plan we recommend due to the number of issues users have had with it.

Now your questions.

all websites were migrated perfectly but the one with your plugin did not migrate. after communicating with support for to many days they asked me to disabled all plugins and i did but they told me there is still a php code running in php.ini

Event Espresso does not alter php.ini files, ever, so I’m not really sure why support would say this is due to Event Espresso?

What is the actual problem they are running into?

They told you to disable all plugins (which I assume include Event Espresso) which means none of those plugin’s code is running on the server, yet it’s still an issue with Event Espresso? I’m not sure how that works, can you add more details on what the issue is?

the following are the text in php.in i wanted to know if there is anything in the code related to the plugin? and if yes can you rewrite it to maintain the plug in working while its not very different from the original php.in so it can migrate without issues?

None of those PHP options relate to Event Espresso with the exception of allow_url_fopen but that will only prevent the images/css from loading on the PDFs.

php.ini changes the PHP config on the server, so if you are moving to a different PHP version, do you need those options changed?


Khalid Joharji

April 17, 2020 at 7:23 pm

Dear Tony,

So I followed the link you provided and I ended up signing up with WP Engine as per your recommendation list and finalized the migration perfectly with their support.

I got to say that after dealing with Godaddy for 10 years my expereince with WP Engine is a whole lot different. I litterly spent hours with Godaddy support trying to do the migration 8 times but none of the 23 support agents helped, the worse thing that i had to explain everything to each agent individually and everytime i get answers that are different or been given before. i even paid a migration fee of 99$ to migrate from the old hosting to managed wordpress, and they refunded that and told me they cant do it, and ended up saying that php.ini had an extra code that causing a problem and that this is out of their support scope to help and i have to check with the plugin creator. seems to me they been trying to ditch me away along the road and I finally did move out.

but with WP Engine I had two online live meetings and 3 agents who responded to different issues all in few hours and as i went through their articles and all their answers where spot on.

I think godaddy once moved their support out-side of the U.S. things got ugly.

Thanks for your support


Tony

  • Support Staff

April 18, 2020 at 7:29 am

Great!

I’m glad that first, you’ve moved away from GoDaddy (they are fine for some things, but GoDaddy Managed WordPress + eCommerce like EE is definitely a no go in my opinion) and secondly had a good experience with WP Engine and are now up and running.

You did request they stop caching EE core pages right?

You’ll likely want to enable WP Heartbeat on the thank you page as well.

More details for both are here:

https://eventespresso.com/wiki/setup-wpengine-hosting-event-espresso/

The experience you posted is one we’ve heard a few times with GoDaddy and is one of the reasons we started advising against using them.

Anyway, I’m glad you’ve moved and it hopefully should continue to be a better experience for you.

Any further questions for EE just let us know.


Khalid Joharji

April 19, 2020 at 9:08 pm

I just asked them to do so, they asked me which pages and i refered them to the 4 critical pages of EE which are

https://www.domain.com/registration-checkout/
https://www.domain.com/transaction-details/
https://www.domain.com/registration-cancelled/
https://www.domain.com/thank-you/

is there any other pages that i need them to execute this on as well?


Tony

  • Support Staff

April 20, 2020 at 6:21 am

If those are the pages that correspond to the pages in Event Espresso -> General Settings -> Critical Pages, then those are the correct pages.

WP Engine disable WP Heartbeat on the server, that will need to be enabled and we have details on the link I gave you above.

Run a test transaction and finalize using any payment method (include an offline one like Invoice), do all of the details load on the thank you page? You should see multiple tables there, if not, then heartbeat is disabled.

You must be logged in to reply to this support post. Sign In or Register for an Account

Support forum for Event Espresso 3 and Event Espresso 4.
Documentation for EE3 and EE4
Documentation for Event Espresso 3 Documentation for Event Espresso 4

Status: publish

Updated by  Tony 1 month, 1 week ago ago

Topic Tags

Notifications

This topic is: not resolved
Do NOT follow this link or you will be banned from the site!