• Resolved rtpHarry

    (@rtpharry)


    Hey,

    I have just started setting this up for my client. It seems like it will do the job but I had a number of teething issues so here is my constructive feedback notes for a first-time technical user:

    Let me have empty values, I didn’t want the second sign up message, or the address, or the phone number but setting them to an empty value just resets back on save. Putting a space in kind of works but then you get an empty row still there.

    Put classes on the different contact detail rows so I can target them with custom css.

    Add a setting for text colours in the admin, I set the background to white as per clients request and all text is unreadable unless I write custom css.

    Putting the custom sign up form in needs work. It should be wrapped in an li tag automatically for a start, but ive got some wierd behaviour now. I wrapped it in an li tag myself so it appears but then the contact stuff doesnt and I’ve unticked most of the options so it seems like there is no way for that contact detail slide to display? Not that I want it as a slide, it seems like it should just be a footer.

    Don’t enqueue the countdown google font when countdown isnt enabled

    Tip: you can combine the font tags into one single request to make it more optimised by joining the font names together (check google fonts for an example by ticking multiple fonts and see how they generate the tag)

    “build it” / “build in” – some typos where you refer to the built-in form – should be built-in not the two phrases you have used

    Hope these notes help you to continue to improve your product ?? Thank you for releasing your work, it has saved me a lot of time.

    • This topic was modified 6 years, 2 months ago by rtpHarry.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Hi!
    THANK YOU so much for the detailed feedback. People rarely take the time to let us know what’s good/bad and we really can’t know unless they tell us ??

    Some of the things you noted are already on our to-do list and should be available in the next release. Others will be in the one after it ??

    Not allowing empty fields is really annoying, I know. And it looked like an easy fix but due to the code we inherited from another developer it turned out not to be. We’ll definitely fix that in the next release.

    Thank you again!

    Some of the things you noted have been fixed in v1.35 (will be out on Monday). Other’s will be in next release. Especially the “leave blank” issue which is proving to be a hard nut to crack due to the old settings lib we’re using. But we’ll get to it ??

    Again, thank you for all the notes!

    • This reply was modified 6 years, 1 month ago by WebFactory.
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Feedback after initial use’ is closed to new replies.