Open API

OpenAPI version 2 is now released with a number of endpoints for sites on Treepl version 7.

Here is a link to the OpenAPI documentation:
https://docs.webinone.com/open-api-admin
and:
https://docs.webinone.com/open-api-frontend

Webhooks

After setting up an API application under ‘Settings’ > ‘API Application’, you can configure your Webhook on the “Webhooks” tab (https://prnt.sc/g_UDGnzrmDcF).

Choosing the entity/item type will then display the available actions (OnCreate, OnUpdate, OnDelete, OnTrigger) and if applicable, the modules/collections to receive webhooks - allowing you to enable just the modules you need to work with Webhooks.

Webhook documentation is here:

https://docs.webinone.com/webhooks

Admin Roles: 'Abandoned Cart Reports' Restriction Incorrectly Displayed

1. Go to any site without the "Abandoned Cart Recovery" extension.
2. Navigate to Admin Roles.
3. The "Abandoned Cart Reports" restriction should not be displayed.
4. Additionally, the "Abandoned Cart Emails" restriction has been fixed.

Screenshot for reference: Link to screenshot

Orders: Internal Error When Setting Negative Product  Units

1. Go to the Orders section.
2. Create a new order.
3. Open the order details and navigate to the Products tab.
4. Open the toolbox for adding products.
5. Select any product (Screenshot for reference: Link).
6. Change the units to a negative value (validation works and the SAVE button is inactive) (Screenshot for reference: Link).
7. Change the product without changing the units.
8. Change the units value (Screenshot for reference: Link).
9. Click SAVE (Screenshot for reference: Link).

Result: An internal error is displayed (Screenshot for reference: Link).

Module Item: Enable Draft

If the draft version of a page is enabled (Screenshot for reference: Link) while the live version is disabled (Screenshot for reference: Link), the draft preview will result in a 404 error (Screenshot for reference: Link).

Cancel on Bambora and PayPal Redirect

1. Set up Bambora or PayPal redirect on the site.
2. Add one product to the cart and choose to pay by Credit Card (Bambora).
3. After being redirected to Bambora, click Cancel (Screenshot for reference: Link).
4. On the checkout page, choose "Cash" as the payment method (Screenshot for reference: Link).
5. In the admin panel, the order is displayed with "None" as the payment status (Screenshot for reference: Link).

Authorize.Net: Paid Secure Zone + Free Secure Zone Issue

1. Set up Authorize.Net on the site to provide one-day access.
2. Create a form that includes both a free secure zone and a paid secure zone.
3. Submit this form.
4. In the user's Subscribes, the free secure zone is not applied; only the paid secure zone is applied (Screenshot for reference: Link).

Roles for Portal Users: Display Informative Error

When a Portal user attempts to add their email to an Admin user:

1. Display an error.
2. The error popup should contain an informative message stating that this user cannot be added as an Admin user because they are a Portal user in some portal (Screenshot for reference: Link).

504 Gateway Timeout: Deleting Large Folder in File Manager

1. Go to the File Manager.
2. Try to delete a folder that is approximately 1 GB in size (Screenshot for reference: Link).
3. After removing some large folders (Screenshot for reference: Link), a 500 error (Screenshot for reference: Link) or 504 error will be displayed.

Forms: Assigned CRM Groups Issue

1. Create two different CRM groups: one applied to "Form Submissions" and the other to "Event Booking" (Screenshot for reference: Link).
2. Go to Forms and create a new form.
3. Assign both CRM groups to the created form (Screenshot for reference: Link).
4. Submit the form from the frontend.
5. Go to Form Submissions.
6. The "Event Booking" CRM group should not be applied to form submissions (Screenshot for reference: Link).

The same issue occurs with event bookings, where the "Form Submissions" CRM group should not be applied to event bookings (Screenshot for reference: Link).

Catalogs: Deleting Assigned Catalog Issue

1. Go to Catalogs.
2. Create a new catalog.
3. Assign this new catalog to any product (Screenshot for reference: Link).
4. Delete the assigned catalog.

Expected: An alert should be shown indicating the catalog is assigned to a product (Screenshot for reference: Link).

Actual:

• The catalog was deleted.
• In the list view, the product shows an empty URL tab (Screenshot for reference: Link).
• On the frontend, the product page is unavailable (Screenshot for reference: Link).

Product: Add to Cart Deleted Product

1. Go to Products in the admin.
2. Create a new product.
3. Go to the frontend to view this product.
4. Delete the product in the admin (Screenshot for reference: Link,Link).
5. Attempt to add this product to the shopping cart on the frontend.

Result: An error is shown when trying to add the deleted product to the cart (Screenshot for reference: Link).

Payment: PayPal Flow ID Issue

1. Go to the Payment section.
2. Create a PayPal flow (Screenshot for reference: Link).
3. The created PayPal flow initially has an ID of 0 (Screenshot for reference: Link).
4. Reload the page.
5. On the GET request for all payments, the PayPal flow now has a proper ID number (Screenshot for reference: Link).
6. This ID is then used for the delete request (Screenshot for reference: Link).

Display Zero Values After Decimal Point in Prices

1. Ensure that prices and totals are displayed with two decimal places, showing .00 after the decimal point (Screenshot for reference: Link).
2. Apply a discount and check the displayed price, which should also show .00 after the decimal point (Screenshot for reference: Link).
3. When JavaScript sends a request to:
   

   /public/api/forms/calculate-form-totalcost?‌Price=29&‌GiftVoucherCode=&‌DiscountCode=&‌Quantity=&‌EventId=0&‌FormAlias=patriot_membership_d

4. After receiving the response, JavaScript updates the displayed price, ensuring it shows two decimal places.

Forms: Quote Form Should Not Include 'Accept Event Booking' Field

1. Go to the Forms section.
2. Create a generic form and include the "Accept Event Booking" field.
3. Change the form type to "Quote".
4. Click Save (Screenshot for reference: Link).

Expected Result:

• The "Quote" form should not have the "Accept Event Booking" field (Screenshot for reference: Link).
• An error should be displayed indicating that the "Accept Event Booking" field is not allowed in a "Quote" form (Screenshot for reference: Link).

Module Item: URL Duplicates (Inactive) Issue

1. Go to Misc Settings and uncheck the checkbox (Screenshot for reference: Link).
2. Go to the Custom Module and create an item (Screenshot for reference: Link).
3. Go to Pages and create a page folder and a page with the same name as the custom module item (Screenshot for reference: Link).
4. Both items should display a "duplicate warning" (Screenshots for reference: Link 1,Link 2).

Results:

• The custom module item has a higher priority than the page.
• If you click preview, the frontend shows the content of the custom module item (Screenshot for reference: Link).
• If you set the custom module item to inactive (by choosing a future date for the release date) (Screenshot for reference: Link), the page content does not show on the frontend, and instead, a 404 page is displayed (Screenshot for reference: Link).
• If you change the URL of the custom module item and set it to active (by choosing a past date for the release date) (Screenshot for reference: Link), the page content is shown on the frontend (Screenshot for reference: Link).

Custom Report: Internal Error When Using Duplicate Field Names

1. Go to Forms.
2. Create a new form with default and custom fields having the same names (e.g., "Address") (Screenshot for reference: Link).
3. Submit this form from the frontend.
4. Go to Custom Reports.
5. Create a new report with the type "Contacts and Cases" and use the submitted form as a filter (Screenshot for reference: Link).
6. Go to the Fields tab and select both checkboxes for "Address" (Screenshot for reference: Link).
7. Go to the Results tab, where an internal error is displayed (Screenshot for reference: Link).

Email Marketing: Incorrect CreateDateTime Value in Email Campaigns

1. Go to Email Marketing.
2. Create a new mailing list.
3. Go to Email Campaigns.
4. Create a new campaign.
5. Observe the CreateDateTime option on both the list and detail views, which displays an incorrect value (Screenshots for reference: Link 1,Link 2).

History: Preview Button Not Working

1. Log in to the admin panel
2. Go to Event settings and enable the Rollback extension.
3. Go to the event item and make some changes.
4. Open the history window and try to click the Preview button.

Result: An error is displayed when clicking the Preview button (Screenshot for reference: Link).

Order: Incorrect Shipping Option Calculation

1. Create a new tax (Screenshot for reference: Link).
2. Create a new shipping option with the applied tax (Screenshot for reference: Link).
3. Create a new order.
4. Go to the PRODUCTS tab and add any product.
5. Select the created shipping option (Screenshot for reference: Link).

Result:

• The total cost is not calculated correctly (Screenshot for reference: Link). The total should be $37.25.
• From the frontend, the calculation is correct.
• The shipping price does not recalculate when the shipping option is set up, only when something else is updated (Screenshot for reference: Link).

Portal: Site Copying Issue with Extensions

1. Copy a site that includes extensions.
2. Check the admin panel: the extensions remain enabled (Screenshot for reference: Link).
3. Check the portal: the extensions are disabled (Screenshot for reference: Link).

Admin Roles: Remove Extra Restrictions

1. Go to Admin Roles.
2. Observe that extra restrictions are being added (Screenshots for reference: Link 1,Link 2).

Expected Result: The following restrictions should be removed from Admin Roles, as they are unnecessary:

• Menus
• ContentTemplates
• Snippets
• Forms
• Contacts
• AdvancedCrmGroups
• Workflows
• WorkflowEmails
• EmailTemplates
• EmailCampaigns
• MailingLists
• AdminUsers
• AdminUserRoles
• Taxes

Current Issue: These extra restrictions are appearing in various sections (Screenshot for reference: Link).

eCommerce: System Properties of Products Not Resetting to Zero

1. Go to any product.
2. Change the values in the system properties fields (Screenshot for reference: Link) and click SAVE.
3. Clear those fields and click SAVE again (Screenshot for reference: Link).

Expected Result: The values should be reset to 0, similar to the behavior in stage v5 (Screenshots for reference: Link 1,Link 2).

Actual Result: After saving, the fields are restored with the last values instead of being reset to 0 (Screenshot for reference: Link).

Workflows: Incorrect Error Text Displayed

1. Go to Comment Settings.
2. Add a workflow notification to any module (Screenshot for reference: Link).
3. Click SAVE.
4. Go to Workflows.
5. Delete the workflow selected in the comments (Screenshot for reference: Link).

Result: An error is displayed with incorrect text referring to forms instead of the relevant module (Screenshot for reference: Link).

Event Group: Naming Consistency

Issue: In the module names, which consist of two words, both words are capitalized except for "Event Group," where "group" is written in lowercase.

1. Module names with inconsistent capitalization (Screenshots for reference: Link 1,Link 2).
2. "Event Group" is displayed with "group" in lowercase (Screenshot for reference: Link).
3. In the dropdown menu for modules, all names are capitalized except for "Event Group," which starts with a lowercase letter (Screenshot for reference: Link).

Expected Result:

• "Event Group" should be consistently capitalized as "Event Group" in all instances, aligning with the naming convention used for other modules.

Forms: Inconsistent Aliases Between Admin and FTP

1. Go to Forms.
2. Create a form with a multi-word name from the admin panel (Screenshot for reference: Link). The alias is generated with an underscore.
3. Create a form with a multi-word name from FTP (Screenshots for reference: Link 1,Link 2). The alias is generated with a dash.
4. Observe that forms created from the admin and FTP have different aliases (Screenshot for reference: Link).

Expected Result: Forms created via FTP should use the same alias format as forms created in the admin panel, with underscores.

Actual Result: Forms created via FTP have dashes in their aliases, whereas forms created via the admin panel have underscores.

Custom Module: Creating Items from Frontend with Enabled Bookings

1. Go to Custom Module settings.
2. Enable bookings (Screenshot for reference: Link).
3. Create a new module item from the admin and add a form for creating module items from the frontend on any page.

Result:

• In the admin, the "Event Date End" field is required (Screenshot for reference: Link).
• In the form for creating an item from the frontend, this field is not required (Screenshot for reference: Link).

Screen recording for reference.

Misc Settings: Inconsistent Use of Dots at the End of Sentences

1. Go to Misc Settings.
2. Observe that two select options have a dot at the end of the sentence, while the other two do not (Screenshot for reference: Link).

Expected Result: All select options should have consistent punctuation, either with or without dots at the end of the sentences.

Custom Module: Parent/Child Table List View Issue

1. Go to the custom module with the parent-child relationship (Screenshot for reference: Link).
2. Go to the table tab in the child module and add a new table (Screenshot for reference: Link).
3. Go to the parent module with the items list view (Screenshot for reference: Link).

Expected Result: The child table should be displayed only in the tree view.

Actual Result: The child table is displayed in the items list view of the parent module (Screenshot for reference: Link).

Products: Incorrect Volume Discount Calculation

1. Create a new product.
2. Go to the Price tab.
3. Create a new price with a volume discount, but ensure it is disabled (Screenshot for reference: Link,Link).
4. Go to the frontend for this product and increase the quantity to 5 to get the discount.

Result:

• The displayed price for 5 products is incorrect (Screenshots for reference: Link 1,Link 2).

Screen recording for reference.

Security Bug with Comments: Liquid Tags Rendering Issue

1. Go to the comments section.
2. Enter a comment containing Liquid tags, such as {{this}} or {% endraw %} {{this}} {% raw %}.
3. Submit the comment.

Original request:
Possible Security Bug With Comments

When using the Comments module and submitting a comment, the CMS wraps the body text in Liquid RAW tags if there is Liquid present in the text. However, it's possible to get around this by adding opposing RAW tags around the Liquid to be injected. eg:

Some text {% endraw %} {{this}} {% raw %} more text...

I've tried this with regular forms and it is not successful and the CMS correctly blocks the Liquid injection attempt (I think by removing the submitted RAW tags).

So perhaps the Comments form needs an upgrade to the same security features used for regular forms.

Import/Export Parent/Child Module: Connection Issue

1. Go to the Parent module settings atthis link.
2. Export the Parent module (Screenshot for reference: Link).
3. Go to the stage environment and import the module atthis link.
4. After the import, observe that the connection between the parent and child modules is not displayed (Screenshot for reference: Link).

Expected Result: The connection between the parent and child modules should be preserved and displayed after importing the module.

Actual Result: The connection between the parent and child modules is not displayed after the import.

Comments: Default Item Limit Shows Strange Number in Liquid Output

1. Use the Comment component in Liquid without specifying a limit value for comments or commentThreads.
2. Observe the Pagination.ItemsPerPage in the Liquid output.

Expected Result: If the limit value is not specified, the Pagination.ItemsPerPage should show a reasonable default value.

Actual Result: The Pagination.ItemsPerPage shows a very large number when the limit value is not specified (Screenshots for reference: Link 1,Link 2).

Additional Information: When the limit parameter is specified, it correctly shows the specified value.

Event Subscribers: Incorrect Display of Capacity in Event List

1. Create a free event.
2. Open the event page in two separate tabs.
3. In the first tab, fill in all fields and click Send.
4. In the second tab, fill in all fields and click Send.
5. Go to the Bookings tab and observe the displayed quantity.
6. Go to the list of Events and observe the displayed capacity.

Expected Result: The capacity should be correctly updated and displayed in both the Bookings tab and the list of Events.

Actual Result: The Bookings tab displays the correct quantity, but the list of Events shows an incorrect capacity.

System/Custom Modules: Internal Error When All Columns Are Deleted

1. Go to any module.
2. Open the Settings and navigate to the Tables section.
3. Delete all columns (Screenshot for reference: Link).
4. Go to Module Items.

Expected Result: The module items should be displayed without errors.

Actual Result: An internal error is displayed (Screenshot for reference: Link).

"Events: Add Pagination to Follow-Up Tab

1. Go to the Events module settings.
2. Navigate to the Follow-Up tab (Screenshot for reference: Link).

Expected Result: Pagination should be added to the Follow-Up tab for better navigation and user experience.

Actual Result: Currently, there is no pagination on this page, which can make it difficult to navigate through a large number of follow-ups.

Comments: Inconsistent Capitalization in 'Comment Sending Policy' Dropdown

1. Go to the Comments section.
2. Navigate to Comments Settings.
3. Click on the "Comment sending policy" dropdown (Screenshot for reference: Link).

Expected Result: The dropdown values should be consistently spelled with proper capitalization.

Actual Result: The two values are spelled differently, with one using capital letters and the other not (Screenshot for reference: Link).

Comments: Inconsistent Capitalization in 'Comment Sending Policy' Dropdown

1. Go to the Comments section.
2. Navigate to Comments Settings.
3. Click on the "Comment Sending Policy" dropdown (Screenshot for reference: Link).

Expected Result: The dropdown values should be consistently capitalized.

Actual Result: The two values are spelled differently, with one using capital letters and the other not (Screenshot for reference: Link).

Custom Report: Inconsistent Capitalization in 'Fields' Tab

1. Create a CRM group and apply it to every select (Screenshot for reference: Link).
2. Go to any custom report.
3. Navigate to the "Fields" tab.
4. Observe the names of each block. The word "Fields" is written with a capital letter, while the CRM groups use a lowercase letter (Screenshot for reference: Link).

Expected Result: The capitalization should be consistent, with either both words capitalized or both in lowercase.

Actual Result: The word "Fields" is written with a capital letter, while the CRM groups use a lowercase letter.

Events: Missing Validation for Follow-Up Emails with Same Name

1. Go to the Events module settings.
2. Navigate to the Follow-Up tab (Screenshot for reference: Link).
3. Create a new follow-up email (Screenshot for reference: Link).
4. Create a second follow-up email with the same name.

Expected Result: An error or validation message should be displayed, preventing the creation of two follow-up emails with the same name.

Actual Result: Two follow-up emails with the same name were created without validation (Screenshot for reference: Link).

All Templates: Add Error Message on Thank You Page

Add validation to display an error message on the thank you page for all templates. This ensures that if a user submits a form and an error occurs, or if a user reloads the thank you page, an appropriate error message is shown.

Steps to Implement:

1. Go to the system pages settings, specifically the Thank You page (Link).
2. Add the following code snippet to the Thank You page template to handle error display:

{% if formSubmissionData == "" or formSubmissionData.error >= 1 %}
<div class="grid-container">
    <h1>Error</h1>
    <p>{{formSubmissionData.errormessages | default : "The form wasn't submitted"}}</p>
    ...

Expected Result:

• When a form is submitted and an error occurs, the thank you page displays an error message.
• When the thank you page is reloaded, an error message is displayed if the form data is invalid or contains errors.

This ensures users are informed about submission errors and prevents confusion when reloading the thank you page.

Backup: Restoring Issues

Issue: Backups are not being restored correctly. After initiating a backup restore, no files or data appear in the File Manager or other parts of the site. Additionally, backups are not deleted properly.

Steps to Reproduce:

1. Go to the backup site: Backup Site.
2. Test on the stage site with ID 32648.
3. Observe that there are backups with storage sizes ranging from 300-900MB.
4. Attempt to restore a backup (Screenshot for reference: Link).

Expected Result:

• Files and data should appear in the File Manager and other parts of the site after restoring the backup.
• Backups should be deleted properly when requested.

Actual Result:

• After restoring a backup, no files or data appear in the File Manager or other parts of the site (Screenshot for reference: Link).
• Backups are not being deleted properly (Screenshot for reference: Link).

Additional Information: Please investigate the issue to ensure backups are restored and deleted correctly.

System Pages: SEO URL Mappings Display Double Slashes

1. Go to any system page.
2. Navigate to the SEO settings (Example link).
3. Open the request SEO settings.

Expected Result:

• The UrlMappings should display a single /.

Actual Result:

• The UrlMappings display double slashes // (Screenshot for reference: Link).

Action Required:

• Investigate and correct the URL mapping to ensure it displays only a single /.

System Pages: CodeView/WYSIWYG Switching Issue

Issue: On system pages, switching between CodeView and WYSIWYG sends the correct values (true/false) in the request. However, after reloading the page, it always opens in WYSIWYG mode.

Steps to Reproduce:

1. Go to any system page.
2. Switch between CodeView and WYSIWYG.

• The correct values (true/false) are sent in the request (Screenshots for reference: Link 1,Link 2).

1. Reload the page.

Expected Result:

• The editor should remember the last selected mode (CodeView or WYSIWYG) and open in that mode after reloading the page.

Actual Result:

• After reloading the page, it always opens in WYSIWYG mode, regardless of the last selected mode.

Action Required:

• Investigate and fix the issue to ensure the editor remembers and opens in the last selected mode after reloading the page.

Orders: Internal Error When Quickly Disabling Gift Certificate and Discount Code

1. Create a new order.
2. Add any product to the order.
3. Add a discount code and a gift voucher to the order.
4. Quickly disable the gift certificate and discount code without waiting for a response from the server.

Expected Result:

• The system should handle the quick disable actions gracefully without causing any errors.

Actual Result:

• An internal error is shown (Screenshot for reference: Link).

Additional Information:

• Screen recording of the issue.

Action Required:

• Investigate and fix the issue to ensure that the system can handle rapid disable actions without causing an internal error.

Forms: Inconsistent Naming for reCaptcha Fields

1. Go to Forms.
2. Create a new form.
3. Add reCaptcha v2 and reCaptcha v3 fields to the form.

Expected Result:

• The reCaptcha fields should have consistent naming conventions.

Actual Result:

• The reCaptcha fields have different names (Screenshot for reference: Link).

Action Required:

• Ensure that both reCaptcha v2 and reCaptcha v3 fields have consistent and clear naming conventions.