3 results found

1. Prevent bot spamming logs

   We often see a lot of errors in the application logs related to bots spamming the website with URL requests that do not even exist, quite often these end in .php extension; example: https://[ConfiguredCommerceURL]/admin/function.php. These seem to be attacks that try to find vulnerabilities on the website. While often times these are harmless, they do pollute the application logs, making it harder for developers to find actual errors that are worth reporting. This feature request is to simply capture that kind of spam requests and simply block them, without processing anything else (these often come with errors such as 'Unity.Exceptions.InvalidRegistrationException' that arise from trying to find dependencies), upon finding out that the request is simply not valid as there should simply not exist any PHP resources on a Configured Commerce website, they should simply be blocked without actually logging an error. If we want to keep these maybe they should be logged somewhere else than the application logs so they could be more easily analyzed? maybe a list of these requests including the origin IP address.

   We often see a lot of errors in the application logs related to bots spamming the website with URL requests that do not even exist, quite often these end in .php extension; example: https://[ConfiguredCommerceURL]/admin/function.php. These seem to be attacks that try to find vulnerabilities on the website. While often times these are harmless, they do pollute the application logs, making it harder for developers to find actual errors that are worth reporting. This feature request is to simply capture that kind of spam requests and simply block them, without processing anything else (these often come with errors such as 'Unity.Exceptions.InvalidRegistrationException'… more

   6 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Research & Design  ·  1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Inherit Product Assignments in Category Hierarchy for Rule Engine

   Current Behavior: In Optimizely, products are currently assigned only to the most specific (end-node) category within a 3-level taxonomy.
   For example, if the category tree is:

   Power Tools > Drills > Cordless Drills

   Then a product like a cordless drill is assigned only to the "Cordless Drills" category, and not to "Drills" or "Power Tools".

   Problem: This structure causes significant limitations when using the rule engine—specifically the “Product In Category” rule. Since products are not assigned to higher-level categories, those categories cannot be used effectively in rules.

   This creates a major pain point when building dynamic catalog restriction groups. Users are forced to assign rules at the lowest-level categories, resulting in excessive manual configuration and a time-consuming setup process.

   Proposed Enhancement: Enable category inheritance within the rule engine so that:

   If a product is assigned to a subcategory, it is implicitly considered part of all its parent categories.

   Rules applied to a higher-level category should automatically include products assigned to any of its descendant categories.

   Benefits:

   Significantly reduces the time and complexity required to build and maintain catalog rules.

   Makes the rule engine more intuitive and aligned with how category hierarchies are conceptually structured.

   Improves scalability and efficiency for merchandisers and admins managing large product catalogs.

   Current Behavior: In Optimizely, products are currently assigned only to the most specific (end-node) category within a 3-level taxonomy.
   For example, if the category tree is:

   Power Tools > Drills > Cordless Drills

   Then a product like a cordless drill is assigned only to the "Cordless Drills" category, and not to "Drills" or "Power Tools".

   Problem: This structure causes significant limitations when using the rule engine—specifically the “Product In Category” rule. Since products are not assigned to higher-level categories, those categories cannot be used effectively in rules.

   This creates a major pain point when building dynamic catalog restriction groups. Users… more

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Research & Design  ·  AdminFilip Åström (Product Manager, Optimizely) responded

   Thank you for submitting this request! We have added this item to our roadmap. Although we cannot guarantee a release date, we expect this feature to be available within the next 12 months.

3. CMS backup

   I'd like to suggest implementing an automated backup system for the CMS to avoid potential data loss or mishaps. Currently, backups can be done manually, which could leave us vulnerable to issues such as data corruption, system failure, or human error.

   Automating backups (daily or even more frequently) with proper versioning and offsite storage would ensure data integrity, minimize downtime, and provide a reliable rollback option in case of any unforeseen events.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Research & Design  ·  2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating