Contact person: Business Client

Phone:Show

Email:Show

Location: Wilmington, United States

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"My SaaS platform (Node.js + MongoDB on a Plesk server) needs several production-level fixes. The very first thing I want addressed is our Chrome extension, so please plan your milestones around that priority.

Chrome extension priorities
• When “New” is chosen in the WordPress drop-down, the extension currently pastes “Used” into the Vehica panel. The value must persist exactly as selected.
• Product images fail to upload completely when the extension pushes listings to the marketplace. They should upload in full resolution and appear in the final listing every time.
• A new front-end template is coming; the extension hasn’t been wired up to it yet, so build in the hooks now so we can switch templates without another rewrite.

Platform / security & admin tasks
• Brute-force password protection: lockouts or rate-limiting to keep credential-stuffing bots out.
• Give end-users a simple “Cancel my account” action that fully closes the account and flags data for removal.
• In the admin panel, Users → Details → View Invoice currently returns a 404. It should load the PDF/HTML invoice normally.
• The “Find Posts” search bar only refreshes the page. Either make it return accurate results or remove it—go with whichever path is quicker and lighter to maintain.

Acceptance criteria
1. All Chrome extension fixes are live in the Chrome Web Store, tested on the latest Chrome build.
2. No SaaS endpoint allows more than N password attempts per X minutes (please suggest best-practice values).
3. Users can self-cancel and receive an automated confirmation email; their status changes in the admin dashboard.
4. View-invoice links resolve correctly for every user record tested.
5. Search bar returns results or is cleanly removed with no dead UI elements.

You will have SSH and Plesk access, repo access (Git), and a staging sub-domain for testing. Please outline your approach and estimated turnaround for the Chrome extension first; the remaining items can follow in a separate commit." (client-provided description)