3

See screenshot

All other fields disappear except the 'Title' field after I save a large block of text with a lot of links in the body (richtext) field.

I can't seem to pinpoint it on to anything specific, this is what I'm putting inside the 'Source' of the richtext http://pastebin.com/jiyA6xii

Any help would be greatly appreciated.

Improve this question
  • This seems to be a bug within Craft. I'd recommend submitting a message to Craft support from your dashboard, along with a copy of your database and log files for the guys to look through. – Jamie Wade Oct 10 '14 at 15:32
  • For what it's worth, I pasted this into a RichText and saved without issue. Do you have devMode turned on? Are you getting any errors in your console or logs upon saving? Logs are found in craft/storage/runtime/logs – Peter Tell Oct 10 '14 at 16:24
  • See answer here: craftcms.stackexchange.com/a/2777/57 – Brad Bell Oct 10 '14 at 17:17
  • Check your browser’s JavaScript console. Are you getting any JS errors on the page? – Brandon Kelly Oct 11 '14 at 16:11
  • @brandonKelly Failed to load resource: net::ERR_CACHE_MISS – nicholasodonnell Oct 13 '14 at 16:11
3

I had a similar problem with disappearing fields in the admin interface, and found it seemed to be something to do with the xdebug PHP extension. Disabling that fixed the problem and the fields reappeared:

sudo php5dismod xdebug
sudo service apache2 restart

The problem in this case is actually to do with reaching a nesting limit, so if you do want to use xdebug, an alternate fix is to bump up the max nesting limit in xdebug's ini file (or php.ini), eg:

xdebug.max_nesting_level=200
Improve this answer
  • 2
    Worth noting that if you update to xDebug 2.3+, the default value has been increased to 256, instead of 100. – Brad Bell Jan 13 '16 at 3:26
2

To anyone wondering, it had to do with the PHP memory limit and max_post_size. If you're coming across this error, increase the limit.

Improve this answer
  • We encountered this with a large matrix field, where blocktypes near the end would lose all their fields. Bumping max_post_size and max_input_vars resolved our issue. – Hraefn Mar 7 '17 at 18:35

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.