Just asking about nuBuilder features.. Topic is solved

[rich3art]

Hi,

I think im not 100% sure about these points below so just thought I'd ask here if thats okay?

I did check the documentation and forum but just want to make sure if nubuilder does have these features or not otherwise how do i implement them?

1. Create a Login & signup page to prevent anyone from accessing the software
2. Create a payments subscription to approve access to software & login
3. Have a feature of 1 to many and also many to many relationships
4. Workflow feature with rest api or something similar to integrate with 3rd party software externally
5. Is it easy to connect to my domain with ssl, I saw i can upload it to my cpanel but how do i connect my domain to that folder, maybe a guide?
6. Does nubuilder have an email sending smtp?
7. Internal communicating/ messaging feature for users to communicate within the app?
8."Ticketing" feature to submit any bugs etc to developers/ myself or how can I implement this?
9. Is there any additional plugins or so i could download and add onto the installation?

Appreciate the help in advance.

Kind Regards,
Richard

[kev1n]

1. A login page is part of nuBuilder. A Signup page can be created as described here.
2. No, I don't know of any plugin, would have to be created by yourself or someone who is able to do it. There's also commercial support or platforms like https://www.freelancer.com/
3. 1 to many: Form/subform relationship. Many to many: Form/Subform + lookups.
4. You can access any REST API with PHPs cURL Extension
5. I'm not familiar with cPanel but I'm sure there are guides in the www or ask for help at e.g. stackoverflow
6. Normally your host provides an SMTP server. nuBuilder allows you to send emails through SMTP.
7. Not included but can be implemented depending on the requirements.
8. Can also be implemented by yourself (done that myself too)
9. There's a "forgot password" addon and additional features can be found in the code library

[rich3art]

Thanks Kevin

[rich3art]

So my only problems will then be nr 2, 7 and 8

Other than freelancer.com/ upwork or other freelancing sites you don't perhaps know of a 3rd party plugin that I can integrate with nubuilder for these points as you mentioned I can use the REST API with PHPs cURL Extension, just so I have some foundation to work with at least then I always hire a freelancer later to upgrade it?

[kev1n]

I am not aware of any 3rd party plugins. At the very least, one would have to know which external services are to be integrated.
Sure, nuBuilder can be extended later practically at will, as it is open source.

[mjd300]

I think I am actually, finally, in a position to help someone else.

Re. 1, I have a working sign-up page, thanks to the info in that thread, and tweaked using the info here.

Re. 2, I am aslo going to set this up. My plan, for simplicity, is to use a 3rd party remote cart (there are numerous options, normally paid services or paid per transaction, where they work via a small piece of javascript code at the point of payment). The trickier part, which I haven't tackled yet, is the connection to get a returned message that payment was successful.

Re. 5, If you have hosting with cPanel, it will already be connected to a domain (you need a domain attached to cpanel to set it up). If your hosting has free SLL (for example, LetsEncrypt) you can add that via cpanel (applies to whole domain). If that doesn't make sense, I'd strongly recommend using your hosting support (if they can't help, you may need better hosting).

[rich3art]

Thanks Mjd, really appreciate the reply, i can't wait until you figure out how to implement the payment feature.

[rich3art]

Hi Kevin

I'm also very curious about your "ticketing" system u said you have up for yourself, will you be willing to share lol?

[kev1n]

The tool is property of my company, so I'm not allowed to share it. In addition, the tool has dependencies with other tables and cannot simply be extracted. Furthermore, there may be different needs and requirements for such a tool depending on the business needs.

I may only share ideas, experience or advice. Basically the ticket tool consists of two Forms: The "request form" where users submit requests and a "supporter form" where support requests are handled.

The two forms share a common table with columns like Ticket/Case Nr, Subject, Description, Created By, Created At, Status, Priority, Reason (maybe Sub reason) and also columns like Response, Response by, Response at etc.

Basic workflow: User submits a ticket -> system sends an email notification to the supporter (supporting group) including a link to the ticket -> supporter sets status (In Progress, Canceled, Resolved, More information required etc.) -> supporter enters a response -> system sends an email notification to the submitter.

Please let me know if you have specific questions I can answer!

[rich3art]

Thanks Kevin, this will help me implement it.

PS Its quite understandable why you not wanting to share it, its no problem, this is already enough to get started.