Feedback

To test your tool, I selected a template that displays correctly in the design stage in Shopify, but when I apply the change and view the site live, it loses its visual effects.

We just ran a test upgrade of our theme (Xtra) from v4.2 to v6.3. We were woefully behind on our upgrades and experiencing theme conflicts. We ran the upgrade and it went into the staging theme area. But A LOT of the PageFly formatting did not appear in the new staging theme area. The site looks really messed up. I was informed that PageFly worked only in the Live theme area. This is a real problem. So here's the urgent request. PageFly needs a way of working on staging themes, and a way to individually target particular staging themes. Thanks!

https://app.crisp.chat/website/7cd1799e-e8eb-476e-8cb7-33778fc41c2a/inbox/session_90f7b6d7-01ac-4189-b056-94b5345a7226/ Cx said: "I especially miss the column and row elements, that allow responsive adaption of the number of items per row. so we will wsitch back to the legacy edtor for now also on your documentation, theres the wrong ifformation for the gen2 editor: https://help.pagefly.io/page-structure-and-elements/editor/user-interface/make-my-page-mobile-responsive#gen-2-layout-how-to-make-mobile-view-responsive "

Hi. I'd like to set up Pagefly sections on the draft theme because we need to preview it before publishing. I hope Pagefly team will develop this function

Looking forward for a way to add Custom CSS or JS codes in header or footer globally for all PageFly pages which will be really helpful in creating multiple pages that requires custom codes as well as integrating third party app codes when using PageFly.

When creating new products, we usually create a draft product and a corresponding PageFly page. But unfortunately, we can't preview everything in combination unless the product is published. Could you please allow attaching the PageFly part to draft products as well?

We would like to report some accessibility issues with the PageFly app. Below is the list of problems that we found. Slideshow element is not properly defined to be used with the screen readers. It is missing necessary role and ARIA attributes. Below is an example of a carousel slider with the AIRA attributes definitions explained. https://www.w3.org/WAI/ARIA/apg/patterns/carousel/examples/carousel-1-prev-next/ It would be great if a Slideshow element had a pause/resume option for the pagination. Tabs element is not properly defined. It is missing proper role and ARIA attributes. Below is an example of tabs with manual controls. https://www.w3.org/WAI/ARIA/apg/patterns/tabs/examples/tabs-manual/ Icon element is missing a textual representation, which makes it invisible for screen readers. It is missing necessary <title> or <desc> elements inside of an SVG.

Just add a tuturiol or video to how to use it for new users so they can understand how to use pagefly

It seems that when you switched to another theme and published it, some corresponding files didn’t transfer properly (not always). This caused certain components not to work or render correctly. I saw this happening for other stores as well (many times). If someone has 100 pages and they switch their theme, sometimes, the pages do not sync. They might need to follow the same process, which is practically very time-consuming and frustrating. Anything we can do about it?

Jahin pointed out about the custom CSS that we need to put into the advanced box to make sure images don't change size and each column has equal width divided into equal portions. He felt this is very technical for a regular person and we can improve it by giving them some kind of control where the image size won't change at all unless they choose to. And the column size is divided in equal portions. For example, if there are 3 columns, each should contain 1/3 of the screen and should not change the width based on content. Previously, it was there, but Jahin felt we needed to bring that back.