Forums

Covering OroCommerce, OroCRM, OroPlatform topics, including community updates and company announcements.

Starting from March 1, 2020 the forum has been switched to the read-only mode. Please head to StackOverflow for support.

Forum Replies Created

Viewing 15 replies - 1 through 15 (of 15 total)
  • Author
    Replies
  • in reply to: Default Price List #40277

    marius.negoescu
    Participant

    Hi, Andrey

    I created the Price List from UI assigned it to a customer and added 1 product price to it and when running the command:

    php bin/console oro:price-lists:recalculate –all –env=prod -vvv

    I get the following error:

    [Doctrine\DBAL\Exception\NotNullConstraintViolationException]
    An exception occurred while executing ‘INSERT INTO oro_cmb_pl_to_pl (sort_order, merge_allowed, combined_price_list_id, price_list_id) VALUES (?, ?, ?, ?)’ with params [0, null, 84, 6]:

    SQLSTATE[23000]: Integrity constraint violation: 1048 Column ‘merge_allowed’ cannot be null

    Price List ID 6 is the default price list, 84 is the combined_price_list_id of the new price list.

    in reply to: Default Price List #40273

    marius.negoescu
    Participant

    I see what you mean.

    If I find anything I will come back.

    in reply to: Default Price List #40269

    marius.negoescu
    Participant

    I have created the price list and price list to customer link from code, so NOT from UI.

    First I created the Price List itself then created the Price List to Customer link.

    Cheers, Marius

    in reply to: Default Price List #40265

    marius.negoescu
    Participant

    When I did that and tried to create new prices lists, when running the command:

    php bin/console oro:price-lists:recalculate –all –env=prod -vvv

    it was generating an error:

    An exception occurred while executing ‘INSERT INTO oro_cmb_pl_to_pl (sort_order, merge_allowed, combined_price_list_id, price_list_id) VALUES (?, ?, ?, ?)’ with params [1, null, 34, 6]: SQLSTATE[23000]: Integrity constraint violation: 1048 Column ‘merge_allowed’ cannot be null

    in reply to: Shipping Freight Class #40102

    marius.negoescu
    Participant

    If you ever do

    composer dump-autoload,

    make sure you do composer install in dev mode to load the classes properly.

    in reply to: Setting up Redis Sentinel #39988

    marius.negoescu
    Participant

    For the second website I have used:

    session_handler: ‘snc_redis.session.handler’
    redis_dsn_session: [‘redis://127.0.0.1:26379/3′,’redis://127.0.0.1:26379/3’]
    redis_dsn_cache: [‘redis://127.0.0.1:26379/4′,’redis://127.0.0.1:26379/4’]
    redis_dsn_doctrine: [‘redis://127.0.0.1:26379/5′,’redis://127.0.0.1:26379/5’]
    redis_setup: ‘sentinel’
    redis_sentinel_master_name: ‘mymaster’
    redis_sentinel_prefer_slave: ‘127.0.0.1’

    I am guessing this is wrong, right ?

    Cheers, Marius

    in reply to: Category Visibility #38961

    marius.negoescu
    Participant

    Any idea how we could setup the visibility so products Visibility To Customer Groups is set as default to Category instead of the Current Product ?

    Cheers< Marius

    in reply to: Category Visibility #38914

    marius.negoescu
    Participant

    So, if I set:

    product TAG3 – Visibility to Customer Groups – Non-Authenticated Visitors = Visibility to All
    product TAG3 – Visibility to All = Category
    category Patient Identification – Visibility to Customer Groups – Non-Authenticated Visitors = Visibility to All
    category Patient Identification – Visibility to All = Parent Category
    category Medical – Visibility to Customer Groups – Non-Authenticated Visitors = Hidden

    This will not make it hidden, right ?

    Cheers, Marius

    in reply to: Category Visibility #38911

    marius.negoescu
    Participant

    It’s actually pretty simple.

    On the demo site here: https://demo.orocommerce.com, I am looking at this product:

    https://demo.orocommerce.com/desktop/medical-tag-sterling-silver-rhodium-plated as a non authenticated user.

    In the admin everything on the product visibility level is pointing to the category level.

    The category level for this product is: All Products / Medical / Patient Identification

    In the Patient Identification the category visibility level is pointing to the parent category, which is Medical.

    I then edited the Medical Visibility to Customer Groups from Visible to All to Hidden for Non-Authenticated Visitors, this should have not allowed me to view the product in question if i was non authenticated, yet I was able to view it.

    Cheers, Marius

    in reply to: Category Visibility #38905

    marius.negoescu
    Participant

    Well, it’s not working.

    I have tried it on the demo site and also on a local version and it’s not inheriting the visibility.

    Cheers, Marius

    in reply to: Meta Titles are not working #38868

    marius.negoescu
    Participant

    Ok, that makes sense.

    If anyone needs to have this working and they don’t have 3.1.x then they should consider switching the columns to get it working.

    Cheers, Marius

    in reply to: Meta Titles are not working #38861

    marius.negoescu
    Participant

    I am using version 3.0.0-rc.

    The problem is I implemented the solution in here https://github.com/oroinc/orocommerce/commit/29298418ffdb01ce2cc35c0d8d2df325ef0afa9b and the export still didn’t work.

    When I modified the columns to use text column instead of string column it worked. The problem might lie within the export iself…

    Cheers, Marius

    in reply to: Meta Titles are not working #38859

    marius.negoescu
    Participant

    What I am trying to say is, the fix you implemented is not working.

    You still can’t export even with the fix you added.

    The export backend header doesn’t contain the string field, only the text field. This is the error that is generating:

    Backend header doesn’t contain fields: metaTitles:default:string

    Cheers, Marius

    in reply to: Meta Titles are not working #38855

    marius.negoescu
    Participant

    I have added the migration schema v1_6 and loaded the migration but it’s still not working.

    php bin/console oro:migration:load –force –bundles=OroSEOBundle

    But the export is still not working.

    I think the issue was supposed to be resolved the other way around.

    The metaTitles should use the text field instead of the string field, not the other way around as in your fix. I tested the use of the text field instead of the string fieldon my local version and it is working fine.

    Cheers, Marius

    in reply to: Meta Titles are not working #38846

    marius.negoescu
    Participant

    Any news on this issue ?

    Cheers, Marius

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

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

Yes No