14
It seems that for whatever reason my 2.5.3 was permitting these forms to function even though "Process form data in Secure Mode?" was set to YES. After the upgrade to 2.7 this restriction began to be enforced on my admin forms as well. The solution comes in two parts:
Add a hidden input field to carry the XID token
Find and use a suitable value to assign ...
12
I'll attempt to keep this answer opinion free!
Your first stop should be the EE3 changelog, and also catching up on the EllisLab blog over the past 6 months. But you'll also need to look at the EE2 changelog to see all the changes since your version that are also included in EE3.
The main changes are the infrastructure and Control Panel but it's where the ...
7
Based on @Max Lazar's comment I was looking over our "logout" code vs.
the code given in EE's documentation and I noticed this difference, we
use this code: Log
Out, but the docs say to use {path='logout'}. Does it matter?
I solved the mystery. The question I made above ^^^ was key and I probably should have just tried it from the get go. Turns out it ...
7
Ok so after 5 hours of banging my head on the table and only getting a nasty bump on my forehead I have a fix that was a 1 second fix.
Basically I had to comment out like this //$config['cookie_prefix'] = ''; in config.php
This all started to happen after I moved from a Plesk environment to a Cpanel setup.
Originally I found the follow code from another ...
6
I would recommend against editing the config file. Instead, it appears you need to include the following line in any that is posting
<input type="hidden" name="XID" value="{XID_HASH}" />
I had the exact same issue when updating from 2.5.2 to 2.8.1. I added that line and all is good. A few simple AJAX POSTs I converted to GETs to also get around this ...
6
Alright, let's do this. I got you, fam. I've done several 2 > 5 upgrades, both small sites and some real big ones.
First thing, so far no client has opted to go the rebuild route. Generally it would take longer than the upgrade process (so more money from them), and I would only recommend it to a site that was in such bad shape (templates are a mess, PHP ...
5
This issue involves the changed security module within EE. Solspace are working on the proper solution however I have also advised them on how to fix this issue (in a different module, facebook connect).
To help them and the community, try this:
Identify the action used to submit the freeform (refer to the exp_actions) table.
Modify the action in ...
4
I think it's a bug, look at this bug report:
https://support.ellislab.com/bugs/detail/19732
Francois
4
Freeform 4.1.3 is not compatible with EE 2.8. Solspace are working on an update.
Adjusting csft_exempt to 1 in the exp_actions table (Freeform - save_form ) got rid of the error so it looks like this has been caused by the security model issue.
4
Yes, the perfect module you want is called ExpressionEngine!
Everything you list is done natively.
New Channel = "Portfolio"
New Category Group called "Portfolio"
Categories as relevant with parents and children
New Field Group containing:
"Description" - Rich text field (or third-party wysiwyg)
"Images" - Grid field with columns for image title, alt ...
4
Replace the continue with return statement.
3
The error has been confirmed as a bug in EE 2.8.
Bug tracker: https://support.ellislab.com/bugs/detail/20165
The issue will be fixed in the next release, and a patch has been posted to the bug tracker for any who need it.
3
For my specific case, it appears to be addons such as Matrix and Assets by Pixel & Tonic that are causing this. By uninstalling the addons I was able to get rid of this error.
3
Add this right above line 194 in admin/expressionengine/libraries/Extensions.php:
$this->EE->load->helper('string');
3
Even if you had a support license, the response from Ellis Labs will be:
Unfortunately we do not provide older copies for download
We do not make older versions of EE available
But there could be light at the end of the tunnel...
Kevin Cupp to the rescue!
3
Bug fix mentioned here
http://support.ellislab.com/bugs/detail/20084
Please make sure these seemingly unrelated settings are set:
The original author’s group has to have “Include Members in PUBLISH page multi-author list?” set to “Yes”
The person attempting to make the edit must have “Can change the author name when > posting channel entries” ...
3
Since your files transferred just fine, it's the database export/import process that failed you.
If you are transferring a database from one server to another it is ideal to do one or both of the following:
Export the database you are duplicating with DROP TABLES syntax and gzipped. If you don't add DROP tables syntax, you'll just merge the tables possibly ...
3
When you upgraded to 2.7, do you recall the first time you accessed admin.php seeing the upgrade screen? And once the upgrade was complete, removing the installer directory?
It sounds like your db has not been upgraded. For example, open your db and check exp_security_hashes table for the 'used' column. Sounds like it is missing. Could be others things ...
3
I received the form expired error message using Freeform 4.2.2 and EE 2.9.2. I added this to config.php:
$config['disable_csrf_protection'] = "y";
The form submitted, but I really didn't want to leave that setting there. I did a little more digging and found that I needed to add a CSRF Token to my form. So I added this hidden input within my freeform tags:
...
3
This may not be the problem but you should definitely get rid of eAccelerator. It's flaky with some PCRE operations (using preg_match() for example) in PHP 5.4 and later. It's possible code changes in EE or one of the add-ons you use have triggered a bug. Use Zend Opcache instead on PHP 5.4+.
Other than that, upgrading to EE 2.9 would likely give you back ...
3
The error points you to line 46 of the Autoloader.php file. That line of code is:
if ( ! isset(static::$instance))
This line of code will only run in PHP 5.3.0 or newer.
ExpressionEngine 2.9 requires PHP 5.3.10 or newer and you're getting the error because your PHP version is older than this.
3
The big daddy of googlemaps add-ons for EE2 is http://devot-ee.com/add-ons/google-maps but afaik there's no seamless upgrade path. You could contact objective html and ask though.
3
that might be all sorts of things. Generally it means there is a php error.
-turn on show errors in the php settings
-turn on show errors in EE
If the main site is showing but the multi sites are not then i think you should place a new version (from the 5.4 zip) of the main index.php for the satellitet sites
2
Safecracker (and Safecracker File fieldtype) is deprecated for EE 2.7+. Read about it here: http://ellislab.com/blog/entry/expressionengine-2.7.0-released
You have to use the native File fieldtype (instead of Safecracker File fieldtype) with the new native Channel Form module.
Then, you need to make sure your Guest member group has permission to post/edit ...
2
It appears the template you should be using is fullarticle_all_weblogs as opposed to fullarticle_all_channels.
For example.
http://professor-murmann.info/index.php/weblog/fullarticle_all_weblogs/1161
vs
http://professor-murmann.info/index.php/weblog/fullarticle_all_channels/1161
2
Check and update all your add-ons first. One of the difference between 2.5.2 & 2.7.3 is that now XID hash code is mandatory for all forms. Many add-ons don't used it before, as result - You are not authorized to perform this action after EE update.
For member_logout function XID is also mandatory.
$xid = ee()->input->get('XID') ? ee()->input-...
2
There's no need to update 1 before upgrading to 2, that's some Cargo Cult voodoo.
That error is specific to the installer attempting to run third_party update routines (often). Temporally remove third_party and try the installer again.
2
Add
$config['disable_csrf_protection'] = "y";
to your config file, you need to add the XID to the form in a hidden field to get rid of the error the other way.
2
I know this one was very obscure and thereby avoided by most readers, but in the event that anyone out there has the same experience, here is the solution.
There were several add-ons that reference /expressionengine/libraries/services_json.php in EE 2.5.5, including Freeform and devot:ee monitor. I had to update these modules to the latest releases BEFORE ...
2
In my old database config file (expressionengine/config/database.php), there was the setting
$db['expressionengine']['cache_on'] = TRUE;
I believe this setting is for db query caching, which is not recommended anymore anyway.
In any case, changing this setting to FALSE, or deleting it, solved the issue for me.
Only top voted, non community-wiki answers of a minimum length are eligible