
Fix website code
- or -
Post a project like this29
£97(approx. $131)
- Posted:
- Proposals: 14
- Remote
- #4467011
- Awarded
Award winning Digital Marketing Expert | SEO Specialist | Website Design & Shopify Consultant
WordPress Developer | Custom Themes, Plugins & E-commerce Solutions,web scraping,Data Entry,Artificial intelligence
✌️#1 SEO Expert |Digital Marketing Specialist| Web Development | Social Media Specialist| WordPress| Wix | Squarespace

⭐ ⭐⭐⭐⭐ Website Developer| WordPress Expert | Graphic Design| MERN Stack & Full-Stack Developer
11892228118221281194588912275455132013011444422121559761209715211935267130019841102168211939783
Description
Experience Level: Entry
Estimated project duration: less than 1 week
I need a WordPress developer to fix a React-based “TCO Intelligence Tool” embedded on my WordPress site (Astra/Elementor). The tool is working for me sometimes, but for normal site visitors the printer fleet list is empty (brands/models show none). My REST endpoint responds, but fleet data is not persisting/serving reliably.
Current setup
WordPress + Astra Child theme + Elementor
Custom REST endpoints in functions.php
GET /wp-json/camelott/v1/fleet (public)
POST /wp-json/camelott/v1/fleet (admin only, stores fleet in WP options table: camelott_fleet_v4)
POST /wp-json/camelott/v1/tco-enquiry (public, sends email via wp_mail + WP Mail SMTP)
The tool runs on a page using inline React/Babel via CDN
Site uses caching/security plugins (NitroPack + Solid Security). Quote/tool endpoints must be excluded from caching.
The issue
Visitors see: {"ok":true,"count":0,"fleet":[]}
I need fleet data to reliably load for ALL visitors and persist server-side.
Admin deploy should correctly save the uploaded fleet to the database (option) and then visitors should immediately see the populated fleet.
What I need you to do
Diagnose why fleet is returning empty for visitors (option not saving, wrong option key, caching, REST blocked, nonce/auth, permissions, CORS, mixed content, etc.).
Implement a robust fix:
Ensure POST saves to the correct WP option (autoload false).
Ensure GET returns the saved fleet consistently for logged-out users.
Ensure caching is bypassed for /wp-json/camelott/v1/* and the tool page (as needed).
Provide a clean, production-safe solution (no hardcoded passwords in the frontend if avoidable).
Confirm with tests:
Logged-out incognito shows brands/models populated.
Fleet persists after refresh and across devices.
No console errors.
Deliverables
Updated functions.php or a small plugin (preferred) implementing the fix safely.
Any required NitroPack/Solid Security exclusion notes.
Short handover explaining what was changed and why.
To apply, please include
Similar WordPress REST API troubleshooting experience
Your approach and expected root causes
An hour ago (local time for Tosin: Fri 10:27 AM)
Hi, thanks for the detailed context, that’s very helpful.
Based on what you’ve shared, this looks like a persistence + caching consistency issue rather than a frontend problem. The two most likely root causes are:
* The POST endpoint is either not reliably saving to the expected option key, or the value is being overwritten / not persisted as expected.
* Redis object caching is serving a stale or empty cached value for the fleet option or the REST response for logged-out users.
My approach would be:
1. Inspect the POST handler to confirm the fleet is being written correctly to the intended WP option (with autoload disabled) and that the value matches what the GET endpoint is reading.
2. Add logging or temporary instrumentation to verify the fleet is truly persisted server-side after “deploy”.
3. Check Redis behavior for get_option() and REST responses and ensure the fleet option and /wp-json/camelott/v1/* endpoints are not being cached incorrectly.
4. Ensure the GET endpoint always returns the saved fleet for unauthenticated users.
5. Add proper cache-bypass rules if needed for Redis and the tool page.
6. Package the fix into a small, production-safe plugin and provide handover notes.
Timeline:
I can complete diagnosis + fix + testing within 24–48 hours.
On pricing:
Given this involves backend REST debugging and Redis object cache behavior, the realistic scope is closer to £97 for a clean, production-safe fix with handover notes and verification across logged-out sessions and devices.
If you’re firm on **£50**, I can attempt a limited-scope fix, but I wouldn’t be able to guarantee full reliability across Redis caching scenarios at that price.
Let me know how you’d like to proceed.
Tosin
Jason B.
An hour ago (local time for Tosin: Fri 10:30 AM)
Ok thats fine, £37.50 deposit an £97. If you send over an amended price and your email for 2fa and I will accept. send you the login details.
Current setup
WordPress + Astra Child theme + Elementor
Custom REST endpoints in functions.php
GET /wp-json/camelott/v1/fleet (public)
POST /wp-json/camelott/v1/fleet (admin only, stores fleet in WP options table: camelott_fleet_v4)
POST /wp-json/camelott/v1/tco-enquiry (public, sends email via wp_mail + WP Mail SMTP)
The tool runs on a page using inline React/Babel via CDN
Site uses caching/security plugins (NitroPack + Solid Security). Quote/tool endpoints must be excluded from caching.
The issue
Visitors see: {"ok":true,"count":0,"fleet":[]}
I need fleet data to reliably load for ALL visitors and persist server-side.
Admin deploy should correctly save the uploaded fleet to the database (option) and then visitors should immediately see the populated fleet.
What I need you to do
Diagnose why fleet is returning empty for visitors (option not saving, wrong option key, caching, REST blocked, nonce/auth, permissions, CORS, mixed content, etc.).
Implement a robust fix:
Ensure POST saves to the correct WP option (autoload false).
Ensure GET returns the saved fleet consistently for logged-out users.
Ensure caching is bypassed for /wp-json/camelott/v1/* and the tool page (as needed).
Provide a clean, production-safe solution (no hardcoded passwords in the frontend if avoidable).
Confirm with tests:
Logged-out incognito shows brands/models populated.
Fleet persists after refresh and across devices.
No console errors.
Deliverables
Updated functions.php or a small plugin (preferred) implementing the fix safely.
Any required NitroPack/Solid Security exclusion notes.
Short handover explaining what was changed and why.
To apply, please include
Similar WordPress REST API troubleshooting experience
Your approach and expected root causes
An hour ago (local time for Tosin: Fri 10:27 AM)
Hi, thanks for the detailed context, that’s very helpful.
Based on what you’ve shared, this looks like a persistence + caching consistency issue rather than a frontend problem. The two most likely root causes are:
* The POST endpoint is either not reliably saving to the expected option key, or the value is being overwritten / not persisted as expected.
* Redis object caching is serving a stale or empty cached value for the fleet option or the REST response for logged-out users.
My approach would be:
1. Inspect the POST handler to confirm the fleet is being written correctly to the intended WP option (with autoload disabled) and that the value matches what the GET endpoint is reading.
2. Add logging or temporary instrumentation to verify the fleet is truly persisted server-side after “deploy”.
3. Check Redis behavior for get_option() and REST responses and ensure the fleet option and /wp-json/camelott/v1/* endpoints are not being cached incorrectly.
4. Ensure the GET endpoint always returns the saved fleet for unauthenticated users.
5. Add proper cache-bypass rules if needed for Redis and the tool page.
6. Package the fix into a small, production-safe plugin and provide handover notes.
Timeline:
I can complete diagnosis + fix + testing within 24–48 hours.
On pricing:
Given this involves backend REST debugging and Redis object cache behavior, the realistic scope is closer to £97 for a clean, production-safe fix with handover notes and verification across logged-out sessions and devices.
If you’re firm on **£50**, I can attempt a limited-scope fix, but I wouldn’t be able to guarantee full reliability across Redis caching scenarios at that price.
Let me know how you’d like to proceed.
Tosin
Jason B.
An hour ago (local time for Tosin: Fri 10:30 AM)
Ok thats fine, £37.50 deposit an £97. If you send over an amended price and your email for 2fa and I will accept. send you the login details.
Jason B.
100% (111)Projects Completed
108
Freelancers worked with
58
Projects awarded
20%
Last project
16 Jan 2026
United Kingdom
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
There are no clarification messages.
We collect cookies to enable the proper functioning and security of our website, and to enhance your experience. By clicking on 'Accept All Cookies', you consent to the use of these cookies. You can change your 'Cookies Settings' at any time. For more information, please read ourCookie Policy
Cookie Settings
Accept All Cookies