Announcement

Collapse
No announcement yet.

Bad server response

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Bad server response

    1) Installing new EspoCRM
    2) Adding field (myname) in Users
    3) Adding layot to "detail" - myname
    4) use crm 1 week
    5) erase layot and field
    6) have notworked crm and "bad server response"

    help

  • #2
    from here of espo.min.js:
    case 200:Espo.Ui.error(self.language.translate("Bad server response")),console.error("Bad server response: "+xhr.responseText)

    Comment


    • #3
      [2014-11-25 08:06:40] Espo.ERROR: Uncaught exception {"exception":"[object] (PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'user.name' in 'field list' at /var/www/crm.vmclouds.ru/application/Espo/ORM/DB/Mapper.php:132)"} []

      Comment


      • #4
        To fix it, go to /custom/Espo/Custom and name "Resources" directory to something like "Resources-old" or just remove it if you don't have any other customization. After that, go to /data/cache and remove "application" directory. Now, it should work.
        Thanks. It will be fixed in a new release.
        Job Offers and Requests

        Comment


        • #5
          Can also happen if the system user account is deleted. To prevent accidental deletion in MySQL use this trigger:

          CREATE TRIGGER `protectsystemaccountbeforedelete` BEFORE DELETE ON `user`
          FOR EACH ROW BEGIN

          IF (OLD.id = 'system')
          THEN
          SIGNAL SQLSTATE '45000' set message_text='Operation Disabled!';
          END IF;

          END

          Comment


          • #6
            Nice suggestion.

            Comment

            Working...
            X