OroCommerce Forums

Covering OroCommerce topics, including community updates and company announcements.

Forums OroCommerce Problem with an ajax call

This topic contains 3 replies, has 2 voices, and was last updated by  Mauro Chojrin 1 week ago.

  • Creator
    Topic
  • #38665

    Mauro Chojrin
    Participant

    Hi:

    I’m having a very weird problem. I just pushed a custom operation that I’ve been developing to production and I noticed there’s a discrepancy in the behavior between the VM and the production server.

    What I’ve noticed is that when I submit a new entry through the form widget in the VM the request looks like this:

    While in the production server it looks like this:

    I don’t know why it is different (the code is exactly the same) but this seems to be preventing the system from executing the method defined in the actions.yml file.

    Another thing I noticed is that in the previous version I had (I’ve been struggling with this for a while), the post was the same as currently on my VM… ¿could there be some cache messing?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Author
    Replies
  • #38666
    Andrey Yatsenko
    Andrey Yatsenko
    Moderator

    You can try to run bin/console oro:platform:update --env=prod to warm up all the caches, synchronize the code with the database state, rebuild all the assets, translations and so on. This is the most reliable way I know, to prepare an application for production after deployment.

    #38670

    Mauro Chojrin
    Participant

    Thanks Andrey. I actually found a little detail… apparently my VM was not in sync with the host code as I thought (I have to check this… I believe I had a problem early on with the autosync and ditched it…).

    I just upgraded to 3.1.6 on my localhost and made sure the upgrade impacted on the VM so at least I now should be running the same code everywhere…

    #40418

    Mauro Chojrin
    Participant

    I recently updated my prod server and the problem didn’t happen again, so I guess there was some issue with the cache.

    I’ll close the issue.

    Thanks!

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

You must be logged in to reply to this topic.

You will be redirected to [title]. Would you like to continue?

Yes No