[Nishit Shan]

in reply to: Custom Works #15909

Hello Andrey,

Thanks !
I can see terminal access and SoapClient extension . I will ask if any this require .

[Nishit Shan]

in reply to: Custom Works #15906

Hello Andrey,

Please provide the terminal access for this domain .

[Nishit Shan]

in reply to: Custom Works #15905

Hello Andrey,

Yes, i got the access !
Can you please confirm if all the required Laravel and PHP packages are installed on the server, especially the SoapClient extension?

[Nishit Shan]

in reply to: Custom Works #15903

Hello Andrey,

I am getting this error while logging into cPanel: “The login is invalid.” It means the login credentials are incorrect.

[Nishit Shan]

in reply to: Custom Works #15896

Hello Andrey,

Any update on beta/test server also you have not yet updated office page and budget .

[Nishit Shan]

in reply to: Custom Works #15892

Hello Andrey,

After Discussion with voip customer and if they approve, please provide a beta/test server where i can migrate the current project and work without effecting our running site.

• This reply was modified 1 day ago by Nishit Shan.

[Nishit Shan]

in reply to: Custom Works #15891

Hello Andrey,

You may discuss this with the VoIP customer for a budget of 1500 NZD; however, please make sure to clearly inform them that this budget will only cover the tasks mentioned in #15888.

For future tasks of this scale, I would recommend considering increase in budget from the beginning.

The accounts team has given me some flexibility to discuss matters with you, including the budget, and I would prefer not to put them in a position where they may need to reconsider that decision.

[Nishit Shan]

in reply to: Custom Works #15888

Hello Andrey,

These tasks will require a minimum budget of 1800 NZD. This budget will include:

* Laravel upgrade (upgrading to the latest version, API optimization, and fixing unnecessary loading performance issues)
* Porting improvements (as described in the task description)
* Porting status display (as described in the task description)
* Porting sent automation (as described in the task description)

Please provide an active customer detail which have data for portout, portin, and all . I just need to see.

• This reply was modified 1 day ago by Nishit Shan.

[Nishit Shan]

in reply to: Custom Works #15886

Hello Andrey,

I can not proceed with this budget. This is not a task where automation can be used to simply upgrade the packages. Even if I attempt to use automation tools to complete the work within 35–40 hours, it is not realistically possible.

Moreover, even if such tools are used just to upgrade Laravel, I cannot assure that the application will run smoothly and without performance issues.

As per my approach, the work is not limited to just upgrading Laravel. It also involves restructuring the API integration flow and optimizing the code for better performance and stability. This is why the timeline I mentioned (35–40 days) is necessary to complete the task properly.

[Nishit Shan]

in reply to: Custom Works #15884

Hello Andrey,

You have allocated only 400 NZD for the Laravel upgrade. As you are already aware, this task will require at least 35 to 40 days of work. This budget is not sufficient for a task of this scale and complexity.

You are already familiar with the required budget for such time-consuming work, as you have previously paid for a similar task during the EN.com Bootstrap template integration.

Therefore, I am unable to proceed with the project under the current budget.

[Nishit Shan]

in reply to: Custom Works #15879

Hello Andrey,

The api i shared with you in post #15873 was from mybilling.nanotelecom.org not inteliquent .

[Nishit Shan]

in reply to: Custom Works #15873

Hello Andrey,

Could you please contact the Inteliquent API provider and confirm whether there have been any changes in the response structure or response parameters? I have noticed a parameter change in the response for the get_custom_fields_values API — earlier it was text_value for the pin code, and now it appears as db_value.

Please confirm if there have been any such changes. If so, I will need to review all API responses accordingly.

I have already made some minor adjustments on my end and have observed a slight improvement in the homepage loading speed.

[Nishit Shan]

in reply to: Custom Works #15871

Hello Andrey,

Regarding your point that “whatever was built earlier was not done in a smart way with efficient performance starting from database queries and pages,” I would like to clarify that the system was built in a structured and efficient way based on the Laravel version, packages, and best practices available at that time. The technology and ecosystem of Laravel have evolved significantly since then, which is why there is now a difference in approach and performance expectations.

Updating Laravel along with its packages and API code will require at least 35 to 40 days. Please plan the budget accordingly.

I will also keep the current project as a backup and set up a separate environment on a local server or on any beta/test server provided by you.

[Nishit Shan]

in reply to: Custom Works #15859

Hello Andrey,

This is my finding i was making from last 3 days:

Issue Report
I have reviewed the project structure, homepage flow, theme, and settings. Based on this analysis, there are a few key reasons why the site feels slow and why some information may appear inconsistent.

Main Issues Identified
1. Heavy Page Loading
• Multiple database queries are being executed on almost every page load.
• A large number of front-end scripts are being loaded globally, even on pages where they are not required.
• Impact: Increased load times, especially on the homepage and theme-based pages.

2. Content Sourced from Multiple Layers
• Page content is being managed across different sources, including:
◦ Page builder
◦ Theme files
◦ APIs
◦ Custom database queries
• When updates are made in one place without proper synchronization, outdated or inconsistent data may be displayed.

3. Outdated Platform Architecture
• The application is currently running on an older version of Laravel.
• Upgrading to a newer version (e.g., Laravel 13) will require a structured migration process rather than a direct version update.
• Several third-party packages may not be compatible with newer versions and will require updates or replacements.

Required Updates & Improvements
1. Core Platform Upgrade
• Upgrade the application step-by-step from the current Laravel version to a modern compatible stack, eventually reaching Laravel 13.
• This process will require careful migration, testing, and validation at each stage.

2. Server Environment Update
• Upgrade PHP to version 8.3 or higher to support newer Laravel versions.
• Ensure all required server extensions and configurations are aligned with the updated framework.

3. Dependency Management
• Review all existing packages and libraries.
• Update compatible packages and replace outdated or unsupported ones with modern alternatives.

4. Performance Optimization
• Minimize unnecessary processing during page load.
• Implement caching strategies where applicable.
• Load front-end assets conditionally, only where needed.

Additional Note
API integration will require rework using a modern approach. The current implementation relies on outdated methods that are not optimized and contribute to slower execution. Refactoring this layer will be necessary to improve overall performance and maintain compatibility with the upgraded system.

Conclusion
The issues identified are primarily related to architectural limitations, outdated dependencies, and inefficient resource handling. Addressing these through a structured upgrade and optimization plan will significantly improve performance, maintainability, and scalability.

[Nishit Shan]

in reply to: Custom Works #15857

Hello Andrey,

Sorry, I noticed that I mistyped in my earlier message. I mentioned 9 lakh+ data, but I forgot to add the “1” before 9. The correct total is 1,969,082 records.

Out of this, 166,772 + 180,829 + 186,482 + 145,350 + 179,605 + 116,642 = 975,680 records are unnecessary. However, I can assure you that these 975,680 records are not being used or accessed, so they are not affecting the loading performance. Therefore, this is not a concern at the moment. I just wanted to inform you so you are aware of it.

The investigation is taking longer than expected and requires more in-depth research. I may also need to discuss this with my boss and accounts team. If they approve, I will proceed further. I had not informed them earlier because I initially thought this would not take much time, but it is now becoming more time-consuming.

As a suggestion, the newer versions of Laravel have introduced structural changes starting from version 10, and the current version is Laravel 13. Whenever you plan to upgrade, I would recommend not doing just a surface-level update. Instead, align the application with the updated framework structure so that it performs optimally. This may also help improve performance.

This is just my suggestion, and I am open to proceeding based on your recommendation as well.

[Author]

Posts