|
aaharonian
|
March 2, 2014 at 10:34 am
Hello,
I have a problem. I have latest version of EE4 installed and when its active – any users other then administrators can’t create galleries in Nextgen gallery, that is also installed on the website. It does look like a permission issue. Any advise? Nextgen is at the latest version as well.
Also – was wondering – why EE deactivates each time after an update?
|
|
Anonymous
|
March 3, 2014 at 3:02 am
Hi aaharonian,
Thank you for reporting this. I can reproduce the same issue locally so have opened a ticket for the developers to look into this, also added a note to update this thread with any outcome/news.
Also – was wondering – why EE deactivates each time after an update?
EE4 should not be de-activating each time however we do show the ‘About’ page after updates to show any new features etc.
Is EE4 de-activating fully when you update?
Meaning you need to load Dashboard -> Plugins and re-activate from there afterwards?
|
|
aaharonian
|
March 3, 2014 at 9:26 am
Tony, any estimate on when this should be resolved?
Meaning you need to load Dashboard -> Plugins and re-activate from there afterwards?
That is correct. In the last 3 updates it happened twice.
|
|
Garth
|
March 3, 2014 at 2:51 pm
Hi aahoronian,
How are you today? We’re testing a fix later today so hopefully we can have an update for you tomorrow.
-
This reply was modified 10 years, 10 months ago by
 Garth. Reason: wrong thread reply
|
|
aaharonian
|
March 4, 2014 at 12:06 am
Well, Im ok. Just trying to resolve this.
|
|
Anonymous
|
March 4, 2014 at 12:30 pm
Hi aaharonian,
The developers fix works as expected and will be released within the next update.
We found 2 issues relating to this, Editors could view the Event Espresso menu but not access EE and the issue you found relating to NextGen.
Both have been fixed an will be included within an update shortly. Event Espresso 4 is currently designed to be managed by Admins and should therefor not display for roles ‘lower’ than this.
Regarding the de-activation issue, we need to ask a couple of question to help narrow this down.
Have you renamed the EE4 plugins directory at all?
Are any errors displayed when EE4 de-activates?
Could you send a copy of espresso_plugin_activation_errors.html from /wp-content/uploads/espresso/logs/ to support@eventespresso.com for us to investigate or if possible create a temporary login for us to investigate this further?
If so please send using https://staging.eventespresso.com/send-login-details/
|
|
aaharonian
|
March 4, 2014 at 5:48 pm
Well, when I have installed it originally into different folder – because the archive you download from the server would have event-espresso-core-reg.zip name and if you will just use it to install via “upload plugin” method to WP, then the installation dir for EE will be called “event-espresso-core-reg”. Thats what happened in my case. I realized that after missing payment buttons. After that I have deleted the plugin, renamed an archive and reinstalled it again (fixed missing buttons issue). I just checked /wp-content/uploads/espresso/logs/ and only have espresso_log.txt and espresso_error_log.txt there. Will create a user for you and send you details for that in a minute.
|
|
Anonymous
|
March 5, 2014 at 8:29 am
install via “upload plugin” method to WP, then the installation dir for EE will be called “event-espresso-core-reg”.
event-espresso-core-reg is the correct directory for Event Espresso 4 currently.
I can’t access the Plugins page of the site currently, it shows Internal Server Error on the log-in you sent. Can you check if EE4 is listed within the plugins list, if so remove it and upload the latest version available from your Event Espresso account page.
When updating the plugin are you using the Bulk updater or only updating EE?
|
|
aaharonian
|
March 5, 2014 at 10:41 am
Was the permission issue resolved already? It is not active right now, since otherwise I can’t upload any galleries.
|
|
Sidney Harrell
|
March 5, 2014 at 3:25 pm
There are currently a couple tickets left on the 4.1.9 release, which contains the fix for the ticket raised on your issue. We should have those last tickets resolved and 4.1.9 released soon.
|
