Hot answers tagged

11

Jesus Christ, never EVER enter a comma in EE. I bet you brought down gmail yesterday too.


7

You will get that error if you have secure forms enabled, and you submit a form without including a valid XID in the post. More here: http://ellislab.com/blog/entry/putting-the-secure-in-secure-mode-forms Add this to your form: <input type="hidden" name="XID" value="{XID_HASH}"> You can disable secure forms in your config, although this is not ...


6

Big thanks to Joel Bradbury for solving this one. I needed to add $config['disable_csrf_protection'] = 'y'; to my config. Here's why: It'll be because the tokens have been generated on a different base domain, and then it's moved and gotten stuck. Normally they're regenerated when they're detected as expired, but if it see's them as not expired, but ...


5

This one's not worth tracking down the root of to be honest -- this is most definitely not what embeds are for, and I'm not surprised you're hitting an error when trying to load this giant hunk of PHP as an embed. My advice is to work with ExpressionEngine, not against it by cramming dozens of lines of PHP into a template. I'd look at moving your custom ...


5

The most common Publish Page DB error for site where member can publish they entries is happens because spammers registered too many accounts. And Publish page just going down when it trying to load the authors list. In Safecracker you don't have author list field, so it's why this issue is not effected on SC form. But you can tested it just trying to open ...


4

It turns out this error was caused by a misconfiguration of the SSL certificate at the web host's end. After getting the error on Exp:resso Store pages using https, I tested a page load of the home page (a non Store page) and got the same error. I concluded it wasn't an Exp:resso Store specific issue. I eliminated htaccess as the source of the error by ...


4

Turns out, this has nothing to do with Store at all. Found my answer on StackOverflow: Since PHP 5.3.9 there's a new configuration setting called "max_input_vars" which limits the number of input variables. The default setting is 1000. Also check if Suhosin is installed, because there's also a similar setting.


4

ExpressionEngine has a protection against Cross-site Request Forgery - CSRF and a documentation available here. You just have to add that line to your form: <input type="hidden" name="csrf_token" value="{csrf_token}"> And send the data in your AJAX request. I had the same problem today and that fixed it for me.


4

I just encountered this, and found that I had to follow the instructions in this Dreamhost wiki entry to truly enable fileinfo functions. (The default "shared" fileinfo support didn't cut it.)


3

Add this right above line 194 in admin/expressionengine/libraries/Extensions.php: $this->EE->load->helper('string');


3

It's an XID issue/bug that is known to EL and slated to be corrected in the next release. A fix until then is posted: https://support.ellislab.com/bugs/detail/19920#12050


3

A couple of things to try: Can you increase PHP's memory limit? Also - since you mentioned Safecracker - is this an older site - and are you using anything other than Channel Images for your images? I've had issues with Imgsizer and switching to CE image helps. Finally, can you either delete or turn off the entry via the db directly to get back into the ...


3

After a little research and a bit of asking around on forums, I found that GoDaddy shared servers were reading the contents of the Security.php file and treating it as malware. I've got in touch with GoDaddy and I'm waiting on a response but this is another reason for me to take my hosting elsewhere... http://ellislab.com/forums/viewthread/244598/


3

It appears that one of the channel fields was at fault. To narrow it down, I removed field by field from the template After the error disappeared, I deleted the channel field and recreated it with the same settings. Now just revert all changes to the template and you're good to go. The error has since disappeared.


3

I wouldn't recommend this but in cases where you have no choice, e.g. you cannot tweak the code in an app in time or something to that effect, you can opt to conditionally disable secure forms in your config.php or bootstrap. E.g. // Make an exception to make AJAX forms app-compatible // EE 2.7.x introduced mandatory XIDs even for AJAX, but an app won't ...


3

/system/codeigniter/system/libraries/Cache/Cache.php Has the Cache class - Check this file is on the staging server, also check the permissions. I've often had similar issues where it's related to case sensitivity and differing servers (my local not being case sensitive, the public servers are) - so also check that the folder and file are in the correct ...


3

The "This site is currently unavailable" error suggests to me the IP addresses or usernames or something has been added to the "banned" list. This is how you check and fix this. --------->>>>>>>> BEFORE YOU PROCEED... BACK UP YOUR DATABASE --------->>>>>>>> THEN BACK THE DATABASE UP AGAIN ============================= Go into the exp_sites table in the ...


3

This is a known bug in 2.9.0 and will probably soonish be fixed in an update See: https://support.ellislab.com/bugs/detail/20462/grid-fieldtype-brings-up-warning-when-rows-are-present-on-entry-submit (ps. bug report includes patch/fix)


3

$plugin_info is a required array for ExpressionEngine 2.x plugins. The PHP class providing the functionality for the plugin will work fine without it, but that is where the information for installed plugins is pulled to be displayed in the control panel. You can find the full details here: ExpressionEngine Plugin API: $plugin_info array e.g.: $plugin_info ...


3

After speaking with Derek privately I was able to resolve the issue which is a permissions error. The steps taken to solve this are: Via FTP/SSH navigate to system/expressionengine/cache and delete everything with the exception of .htaccess and index.html . Afterwards, change your permissions on system/expressionengine/cache to be 777 then restart your ...


3

"Transfer Needs for Europe's Biggest Sides in Summer" isn't an entry_id and should not be in the where in clause. Wygwam is pulling those entry ids from EE's page ids. Check the page module and any config overrides.


3

With that error when uploading a PDF the first thing to take a look at is Admin ‣ Security and Privacy ‣ Security and Sessions and see whether "Apply XSS Filtering to Uploaded Files" is set to "yes." If it is, try setting it to "no" instead. If that clears it up and you don't want to globally stop applying XSS filtering to uploaded files then there is a ...


3

This is a PHP parse error. It's exactly what Derek Hogue said. On line 33 you are trying to use a stdClass as an array in some functionality on a template that has PHP parsing turned on. EE template: Hello from {site_url}! <?php $stdclassvar = new stdClass; echo gettype($stdclassvar); // this outputs "object" $arrayvar = array(); echo gettype($...


3

Umm index.php /* * -------------------------------------------------------------------- * Error Reporting * -------------------------------------------------------------------- * * PHP and database errors are normally displayed dynamically based * on the authorization level of each user accessing your site. * This variable allows the error ...


3

From this post over on EllisLabs : https://ellislab.com/forums/viewthread/81867/ What is happening when that message displays (as you will probably know) is that there is something that is setting cookie/post/session variable with a key that contains a character in the dis-allowed list. Are you sure there's no dodgy characters in the users username or ...


3

Found some suggestions in the EllisLab Forums that might help. In the system/codeigniter/system/core/input.php file: Find the function _clean_input_keys($str) Change: exit(‘Disallowed Key Characters.’); to: exit(‘Disallowed Key Characters.’. $str); This will tell you what characters are causing you problems. Then you can ...


3

I recently encountered the same issue, and it was a tough nut to crack. From the error message, I assumed I was dealing with a missing file – presumably something uploaded via Assets. I first attempted to re-index Assets. That didn't help. Then, I did a grep search for "This file cannot be found" on the /assets folder: $ grep -r "This file cannot be found"...


3

As I said on Slack: put a slash before the URL so it's not relative to the current page like so /performances/category/{category_url_title}


3

You need to change a little in code at line 230 in upd.gmaps of your plugin directory. 'constraint' => '255' to 'constraint' => '191' This need to change from 255 to 191 because there is INNODB utf8mb4.


2

I would check to see if you have mod_security installed on your server. That seeing the http:// in your form post (saving LV) may be triggering the save to be blocked.


Only top voted, non community-wiki answers of a minimum length are eligible