The updates can be categorized into 5 key buckets -
1) thank you pages
2) back-end table labels
3) handling customer/agents/merchants registrations data
4) Handling form validation
5) Updating agents list
1) THANK YOU PAGES
(1.1) Update thank you pages to pop up after the successful submission of the following forms: "become an agent", "become a merchant", "customer registration", "Contact Us" and "share your story". Currently, the thank you pages are not independent pages and the thank you only replaces the forms....rendering/formatted correctly -- all the residual copy/title from the related form page remains with the thank you message. The client didn't like this at all, but I told them we had a registration page, that it was just not served up.
Can we use a thank you page along the lines of the "forgot password' pop up? That pop-up is awesome
(1.2) Let the Thank you page copy read as follows "Thank you [FIRSTNAME] for your submission and interest in my.wallet. A customer care agent will contact you within 24 hours".
2) LABELING OF [url removed, login to view] TARGET SEGMENTS
(2.1) In the back-end database, let's change the following role labels (within WP --> User section):
--> Change "Editor" to "Agent"
--> Change "Contributor" to "Merchant"
--> Change "Subscriber" to "Customer"
3) SUBMISSION OF FORM REGISTRATION DATA
(3.1) Let's change subject line for each registration email to make it easy for FETS to know the registration type
a. Customer Registration --> | email subject line: Customer Registration
b. Become an Agent --> | email subject line: Agent Inquiry
c. Become a Merchant --> | email subject line: Merchant Inquiry
d. Contact Us --> | email subject line: Contact Us Submission
e. Share Your Story --> | email subject line: Share Your Story Submission
For testing purposes, use . Once correct submission is confirmed, change email address to "".
(3.2) Let's disable the posting of agents or merchants front end registration data into the back-end database and send as emails to the client email address only. Clients need to first review and approve the agents or merchants before pushing the information into the look-up table. The client will be responsible for manually updating customer/agent/merchant information into the backend database. Else, "spammy" registrants show up and may embarrass the client.
4) HANDLING FORM VALIDATION ERROR
(4.1) Make the validation error format consistent across all forms. Replicate the format used on the "Contact Us" form across all forms...really looks classy. I thought we had this for the registration form? The mozilla pop-up does not look good coming from us.
5) ABILITY TO UPDATE AGENTS WITHIN WORDPRESS PORTAL (USER SECTION)
(5.1) Let's revert the new user form to the same format as the "editor" forms or the default profile form. This will allow FETS to update the agents list on the fly. The form we had there earlier was fine, just that we should disable the "required" for emails and username. I don't know what happened but let's revert back to that old form and just make emails and username non required fields. Per the comment on 3.2 above, the client will be able to review the registration application from the Agent/merchant and manually update the information themselves
(5.2) Once we make these changes, let's ensure the state drop-down is pulling looking up the state information too. In our test, only the city information is added in the agent list drop-down.
Décerné à :
10 freelance font une offre moyenne de $627 pour ce travail
Consider it done.... Right developers at your door...HIRE WITH CONFIDENCE...Hope to achieve next positive feedback from you!!! Please check you inbox for more info.
I can do your job.I am experianced Joomla/Wordpress/PHP Developer. fast and 100% accurate work. Please check your private message [url removed, login to view]!!