ssossossosso

Forums

Covering OroCRM topics, including community updates and company announcements.  Subscribe

Open-Source CRM software Forums OroCRM OroCRM – Installation/Technical Issues or Problems Roles Update Error in latest dev-master

This topic contains 2 replies, has 2 voices, and was last updated by Spurgeon Spurgeon 2 years, 5 months ago.

  • Creator
    Topic
  • #6409
    Spurgeon
    Spurgeon
    Participant

    Hi,

    Greetings!

    Just noticed that when a custom role is being edited ( route user/role/update/<id> ) nothing happens.

    When checked with browser console, issue turns out to be some incorrect parsing of object property (this->) which results the clicked entity causing 404 errors

    Apparently due to ‘entity/%3A’ instead of ‘entity/’

    This is not the case in another instance where nodejs is not used (js not optimised as oro.min.js).

    Could this be fixed please?

    Thanks!
    warm regards
    Spurgeon

Viewing 2 replies - 1 through 2 (of 2 total)
  • Author
    Replies
  • #6495

    Alexandr Smaga
    Participant

    Hello @spurgeonbj !

    Do you run your instance on your workstation using some LAMP/MAMP environment ?
    We had some issue before with routes that start with security, due to misconfiguration of custom environments.

    #6499
    Spurgeon
    Spurgeon
    Participant

    Hi Alex,

    We have this issue on ubuntu 14.04 with regular mysql & apache2 packages that comes along with Ubuntu.

    But this error didnt come on another virtualbox instance with same ubuntu setup didnt have this issue on the next day. Not sure whether this was fixed in between.

    The only thing that comes to my mind regarding these two variations is nodejs (either present or has a different version of nodejs in one that failed).

    BTW,
    Another quirk I noticed was in having the webroot on symlinked partition. For eg. when I migrated an oro instance from /var/www/crm/crm-application to another server’s /var/www/crm/crm-application.

    The latter /var is actually symlinked /data/var. While apache2 sees this as /var/www/crm… , oro detects this as /data/var/crm and results in 404s.

    Just FYI, if there could be an issue.

    Thanks once again!

    warm regards and gratitude,
    Spurgeon

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.