Fix issues with Facebook API in the OpenCart module

Budget: 1800 UAH Deadline: 2 days

Good day! I can start today. The situation is familiar: when opening the module page, the front starts a synchronization cycle and begins to flood requests to the Graph API — either it's a continuous polling that doesn't stop, or a product enumeration where some items do not have a valid Facebook ID in the catalog, and each such item returns gr:get:InvalidID. Errors multiply because the request is repeated on every render/interval.

Plan: first, I will look at the module logs and network requests on the page (where and how frequently the calls are made), find the initialization point — it's almost always a failed setInterval/recursion or synchronization without checking if the FB-ID exists. Then I will set a guard, remove unnecessary repeats, cache responses, and correctly map/skip items without a valid ID so that InvalidID is not generated at all. I will review the specifications from the Google Doc before starting.

Estimated: diagnostics and localization — on the day of the start, fix and check the stability of requests — another day. Question: will you provide access to the test stand (admin panel + module log files), or are you editing on the production? And what version of OpenCart — 3.x or 4.x?

Budget: 1400 UAH Deadline: 1 day

Hello! I am ready to start working right now. I clearly understand the task and have successful experience in implementing exactly such projects (examples are in the reviews). I will complete the task today, quickly and without unnecessary questions. Let's discuss the details and get started! 🚀

Budget: 700 UAH Deadline: 1 day

Hello! I can start working tomorrow at 10:00, and I expect to resolve the issue within 48 hours. Thank you for your trust.

Budget: 5000 UAH Deadline: 2 days

Hello, Volodymyr!

I have reviewed the description and your Google document. The task is clear: we need to stop the avalanche growth of API requests and eliminate the gr:get:InvalidID errors when opening the module page.

I have been working with OpenCart and the Facebook Graph API / Webhooks integration for a long time. The symptom indicates a loop (infinite polling or incorrect rendering/recursion) when the script tries to poll outdated or invalid object IDs without a stop condition. I will also fix the output of the nickname and followers (likely due to changes in API versions).

⚡ When can I start: I am ready to begin work today / soon.

⏱ How much time is needed: * Day 1: Localization of the problem, analysis of requests and module logs, searching for the loop point.

Day 2: Fix, adding ID validation before sending, testing API stability.

Overall for the work: 1–2 days.

To get started, I will need access to the admin panel (test stand) and FTP/SFTP. I will be happy to help, feel free to message me! Expand

Budget: 1800 UAH Deadline: 1 day

Hello, I can take on the diagnosis and fix the OpenCart integration with Facebook/Instagram. Usually, such problems arise due to incorrect request cycles in the module (self-recursion, duplicate OAuth calls, or improper handling of Webhook/ID parameters). I will check the logs, the place of API call initialization, and the reason for the increase in gr:get:InvalidID, after which I will fix the source of the requests and stabilize the integration without unnecessary API calls.

Budget: 1700 UAH Deadline: 3 days

Good day! I am ready to start today. OpenCart module for Facebook/Instagram integration: I will find the cause of the avalanche of API requests and errors gr:get:InvalidID, add logging/tests, fix the loop/incorrect IDs, and check the webhook/OAuth. Deadline: 3 days.

Budget: 1700 UAH Deadline: 2 days

Good day. I understand the task: in the OpenCart integration module with Facebook and Instagram via API, OAuth, and Webhook, after opening the module page, the number of requests to Facebook starts to grow exponentially, and the number of errors gr:get:InvalidID increases. We need to find the cause and fix it.

I have been working with OpenCart and integrations via API for a long time, so I am familiar with the general mechanism of such a problem. The symptom, when requests start to multiply specifically upon opening the module page, usually indicates either a cycle of repeated calls during page loading (repeated token refresh or polling in a loop without a stop condition), or an invalid object or ID being passed to the Facebook Graph API, which causes InvalidID, after which the logic repeats the request again and again. I will check what exactly is triggered when opening the module, how IDs are formed in requests to the Graph API, and where there is a lack of stopping or caching to eliminate unnecessary calls and the errors themselves.

I will look at your detailed specifications with screenshots in the Google Doc to link the errors to a specific place in the module code. I can start in the near future. Regarding the timeline: first, I need to open the document and look at the module code to specify, but based on experience, a similar fix usually takes a few days, where most of the time is spent on localizing the cause, and the actual fix is usually small.

Please provide access to the module code and the environment where the problem can be reproduced. Is this a custom module or a ready-made one from the marketplace?

Budget: 3000 UAH Deadline: 2 days

Good day! I carefully read the technical specifications — the task is clear.

Two problems are solved separately:
1. Nickname and number of subscribers — most likely changes in the Graph API (v14+) removed fields that were previously returned by default, they need to be explicitly requested.
2. Mass requests with gr:get:InvalidID — most likely the polling script is accessing the API with IDs that no longer exist (deleted messages, pages, or avatars). We need to find where these requests are formed, add ID validation before sending, and remove unnecessary calls.

I can start tomorrow. For diagnostics and fixes — 1-2 days depending on the volume of the module's code.

Budget: 1300 UAH Deadline: 1 day

Good day. I am ready to solve the problem today. I am well acquainted with OpenCart and have experience in developing my own modules.

Budget: 1300 UAH Deadline: 1 day

Hello
I will do it now
Message me privately
We will discuss the details

Budget: 2000 UAH Deadline: 2 days

Hello!

I have reviewed the specifications. I have experience with OpenCart, API integrations, and troubleshooting similar issues where background JS/PHP code generates excessive requests and quickly hits the limits of external services.

I can check which specific function is causing the gr:get:InvalidID requests, add logging for Facebook/API responses, remove incorrect calls without breaking the current functionality of the module, and separately fix the output of the nickname/subscribers. I see in the specifications that an important criterion is that errors should not increase and API limits should not be consumed when the module page is open.

I can start today/tomorrow.

Budget: 1000 UAH Deadline: 1 day

Good day! I am ready to take on the diagnosis and correction of the issue with the Facebook/Instagram API in OpenCart. I can start today.

Budget: 2800 UAH Deadline: 1 day

Good day.

I am ready to take on the task right now.

Work plan:

* I will analyze the OpenCart module and the integration with the Facebook/Instagram API.
* I will find the cause of the mass requests to the Graph API and the errors gr:get:InvalidID.
* I will add detailed logging of problematic requests and Facebook responses.
* I will identify specific functions and files that are causing the limit overages.
* I will fix the display of the user's nickname and the number of subscribers.
* I will check to ensure that the current functionality of the module is not broken after the changes.

Deadline: up to 2 days.
Cost: 2800 UAH.

After receiving access to the code and the module, I can start working immediately today. Expand

Budget: 2000 UAH Deadline: 1 day

With the right setup, the work will take no more than a day. I can start at any time, even now.

Budget: 1400 UAH Deadline: 1 day

Hello! I have relevant experience with similar tasks, and I can help with your project. I can quickly familiarize myself with the requirements, propose the best solution, and execute the work thoroughly. I am ready to discuss the details and get started.

Budget: 2500 UAH Deadline: 1 day

Good day! I have experience with PHP/OpenCart and integrations with Facebook/Instagram Graph API, OAuth, Webhooks.

I read the specifications - both issues (disappearance of the username/followers and API limit leaks with the increase of gr:get:InvalidID) are very likely related to the code that periodically updates the client's profile data (username, number of followers, avatar) through separate API requests while polling unread messages. If the user ID in these requests becomes invalid (for example, due to a change in ID format in the Graph API or an outdated token), each polling cycle generates the error gr:get:InvalidID and consumes the limit.

Work plan:
1. Find the function(s) that make these requests (most likely in the polling script of the admin panel)
2. Add logging of the Facebook request/response to a separate file
3. Determine the exact cause of the invalid ID
4. Fix the request, restore the display of the username and followers
5. Check that the API limits are no longer consumed when the tab is open

Deadline: I will start today, estimated time for diagnostics + fix — 4-6 hours (possibly faster, depending on the structure of the module code).
Estimated cost: 2500-3000 UAH (for the entire scope - diagnostics, logging, fixing both issues, documentation of changes).

I am ready to start with code analysis, please provide access to the module files (FTP/SSH or archive) and the request log if available. Expand