Potentially great software, but needs to be more developer friendly…

  • gerald2023

    (@gerald2023)


    6 months ago

    I have rewritten this review due to making a mistake, some of the below comments might not relate to this review anymore. The html in the “view source” I described before can be ignored now, it was something else.
    ———
    I have the paid version but not the version with the “style manager”. It works great for some things, but there are a couple issues. This program renames things, etc when you update the form and save. If you created custom styles for the form they may have to be reconfigured every time you save a form, I lost 2 hours adding my styles back, then they broke when I saved it again.

    If you are going to buy it I would recommend either getting the version with the style manager or be very careful about how to do your custom css styles. They will break and force you to create them all again.
    Example: I right click and inspect something in the registration form, then in the inspection window right click -> copy -> copy selector
    Then use that to style parts of the form.
    What happens is when I edit the form in the admin pane land save my css no longer works, the selectors have all changed, not sure how but they have and I have to recreate my custom css.
    I use this technique all the time and assume everyone else does, so this plugin should not break that, but I do understand the grids move around.

    Second issue: Adds a bunch of .js files to my site, would rather them be packaged together.

    • This topic was modified 6 months ago by gerald2023.
    • This topic was modified 6 months ago by gerald2023.
    • This topic was modified 5 months, 3 weeks ago by gerald2023.
    • This topic was modified 5 months, 3 weeks ago by gerald2023.
    • This topic was modified 5 months, 3 weeks ago by gerald2023.
    • This topic was modified 5 months, 3 weeks ago by gerald2023.
Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter gerald2023

    (@gerald2023)

    Also, I have 61 javascript files in my “view source”, most of them are from this plugin.

    Plugin Support Sandip Pokhrel

    (@sandippokharel)

    Hi @gerald2023

    Thank you for taking the time to share your feedback on the User Registration plugin. We sincerely apologize for the frustration you’ve encountered with the class and ID renaming, and hidden HTML elements.

    We understand how these issues can significantly impact your workflow and website performance. We take user feedback seriously, and your concerns are valuable to us.

    To get the best possible assistance and find solutions specific to your situation, we highly recommend reaching out to our dedicated support team at https://wpuserregistration.com/. We have checked our platforms and we are unable to find a support ticket regarding this issue.

    We’re confident that by working together with our support team, we can find a solution that optimizes your experience with the User Registration plugin. Meanwhile, we have already mentioned this with our developers.

    Before taking any further action with your one-star rating, we kindly request you to reach out to our support team at the link above. We’re committed to turning this into a positive experience for you.

    If, after interacting with our support team, you feel we’ve addressed your concerns effectively, we’d be incredibly grateful if you would consider revising your review to reflect your improved experience.

    Thank you again for your feedback and for the opportunity to improve our plugin.

    Regards!

    Thread Starter gerald2023

    (@gerald2023)

    If you read the review, and address the issues I bring up, then your software would be more developer friendly and would not need the interaction you are mentioning above. I have been a developer for over 25 years, and I have seen a lot of software good and bad, I have seen just about everything and your plugin is lacking in 3 main areas.

    1. css and id names change on update of form, meaning it is a waste of time to try and custom style the form, the styles will be overwritten as soon as I update the the form and click “save”. It works on things like the fonts, but the div’s that make up the form totally change when I click the save button.
    2. Tons of .js files added to the “view source” of the page, why not group them all together rather than add 50 .js files to my website?
    3. 12 pages of html added to every page of my webstie. If I “view source” I see over 12 pages of random html that is not being used. Extra bloat that I normally do not see in a plugin.

      Your plugin solves a bunch of problems and has a lot of uses, but the above 3 issues are a deal killer for me and I hope my review helps other developers to know what they are buying before they buy it.
    • This reply was modified 5 months, 4 weeks ago by gerald2023.
    • This reply was modified 5 months, 4 weeks ago by gerald2023.
    • This reply was modified 5 months, 4 weeks ago by gerald2023.
    Plugin Support Sandip Pokhrel

    (@sandippokharel)

    Hi @gerald2023

    Thanks for writing back,

    Thanks for the feedback about optimizing the JS and CSS files for the User Registration plugin! We’re constantly working to improve performance.

    To further investigate the HTML page, CSS class, and ID changes you mentioned, we recommend submitting a detailed support ticket through the link we provided earlier. Or, as you already are a premium user, you can create a support ticket from your account. This will allow our team to analyze the issue more effectively and find a solution.

    We appreciate your understanding and look forward to hearing from you through our official support channels.

    Regards!

    Plugin Support Sandip Pokhrel

    (@sandippokharel)

    Hi @gerald2023

    1: Classes and IDs

    Thanks for raising this point! It seems there might be a misunderstanding. Form classes and parent divs typically don’t change with updates. Only grid classes (like ur-grid-1, ur-grid-2) and field IDs (based on form builder settings) might adjust when users add or remove rows/fields. These are designed for flexibility, not due to code changes on our end. Building a form around these dynamic elements is a common approach.

    2: We agree!

    We’ll definitely address the second point you mentioned and we are working on the JS file structure for the plugin.

    3: Need clarification

    The term “12 page HTML” is a bit unclear. Are you referring to divs functioning as separate pages? In the frontend, this isn’t an issue. The backend’s global settings use a structure that hides irrelevant divs and shows the current menu’s section. If you could explain this point further, it would be helpful!

    As mentioned in the other replies, we still suggest you to contact our dedicated support with the details so that we can look into it intensely. 

    Regards!

    Thread Starter gerald2023

    (@gerald2023)

    I have updated the original review after looking a little deeper into this plugin. I think the css selectors changing upset me so much that I saw something that was not there ( the hidden html )

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this review.