XML link, file for Roosevelt, Epcenter

Greetings! I am looking for an experienced WordPress/WooCommerce developer for a small but urgent task. Problem: We are integrating Instagram Shop (Meta). When transitioning from the Instagram shop to the site cart, Meta passes product parameters in its own format: ?products=ID:quantity. Currently, WooCommerce ignores this parameter, and the cart opens empty. What needs to be done:It is necessary to implement a handler (hook on init or through a proper redirect) that will intercept parameters from Meta and convert them into the standard WooCommerce format for adding to the cart: ?add-to-cart=ID&quantity=X. Example logic:Link from Meta: https://treskare.com/cart-2/?products=18446%3A3Should transform/redirect to: https://treskare.com/cart-2/?add-to-cart=18446&quantity=3 There is a basic example of code from our specialist (I will provide it in private messages). It needs to be checked, adapted to our site's theme/plugins, and tested to ensure the cart is filled correctly and there are no conflicts with current user sessions or caching plugins. Requirements for the performer: Excellent knowledge of PHP, WordPress, WooCommerce API.Experience with customizing the WooCommerce cart (cart/checkout).Availability of reviews and successful projects on WordPress. Mandatory testing: The performer must conduct a functionality check of the code. The new setup should not disrupt the standard ordering process on the site. Directly adding products to the cart from the catalog, changing quantities in the cart itself, and proceeding to Checkout must work without errors. Security and code isolation: The code must check for the presence of the products parameter and the correctness of the product ID before executing the redirect to avoid causing Fatal errors or redirect loops for regular site visitors. Work on a test copy (Staging) or backup: Before uploading the code to the "live" site, the performer must demonstrate the script's functionality on a copy of the site OR make a backup of the file being modified. Conditions for acceptance of work and guarantees:Payment is made only after a full functionality check of the code on the site.The project is considered successfully completed only if:The link from Meta correctly adds the product to the cart.The standard functionality of the site is NOT disrupted (normal product addition, order processing, payment/shipping plugin functionality works without failures).If technical errors occur after the code implementation (Fatal error, conflicts with WooCommerce sessions, or order processing fails), the performer is obliged to resolve them within this project at no additional cost.

I want a bot for Telegram. Loading dialogues. With the help of AI, checking for potential lies. A website with advanced features. Registration, API, statistics, etc.

It is necessary to migrate the Opencart online store from PHP 7.4 to PHP 8.x. Currently, the core version is 3.0.3.8. We read that most likely the core will also need to be migrated to version 4.0 and there shouldn't be many difficulties... The functionality is mostly custom, and there are also Simple, OCFilter, Nova Poshta. We are waiting for recommendations and an approximate price. Ideally, someone who has already done similar work.

It is necessary to perform the update, transfer, and configuration of Laravel projects to a new server, ensuring stable operation, security, protection against exploits, and correct functioning of all services after migration. 1. Main tasks Prepare the new server for operation. Transfer project files, databases, configurations, and cron jobs. Update server software. Configure a secure environment for Laravel. Check compatibility of PHP, Laravel, Composer packages, and dependencies. Ensure protection against known exploits, malicious requests, and unauthorized access. Set up SSL certificates. Check the functionality of the websites after the transfer. 2. Transfer of Laravel projects For each project, it is necessary to: Transfer project files. Transfer the database. Transfer the .env configuration. Set directory access permissions: storage bootstrap/cache Check functionality: homepage; admin panel; authorization; forms; API; file uploads; email sending; cron jobs; queue workers.3. Security and protection It is necessary to implement basic and application-level protection: close root access via SSH; configure SSH access only via keys; change the default SSH port if necessary; configure the firewall; allow only necessary ports; install Fail2Ban; hide service versions of Nginx/Apache/PHP; restrict access to .env, .git, backup files, log files; set correct file permissions; check projects for malicious files; check Composer packages for known vulnerabilities; update dependencies if it does not break functionality; configure protection against SQL injection, XSS, CSRF, and path traversal; check the correctness of Laravel APP_ENV and APP_DEBUG; set APP_DEBUG=false in production; configure rate limiting for critical endpoints; check access to storage/uploads; configure protection against PHP execution in upload directories; check access rights to admin panels. 4. SSL and domains It is necessary to: Install SSL certificates. Configure automatic SSL renewal. Enable redirect from HTTP to HTTPS. Check the correct operation of websites via HTTPS. 5. Backup It is necessary to configure backup: project files; databases; .env files; uploaded media; cron configurations; Nginx/Apache configurations. Backup should be performed automatically on a schedule. It is preferable to store copies separately from the main server. 6. Post-transfer verification After migration, it is necessary to check: absence of 500/403/404 errors; absence of critical errors in Laravel logs. 9. Result of execution After the work is completed, there should be: Laravel projects successfully transferred to the new server; websites are functioning stably; SSL is configured; the server is protected with basic security settings; access to critical files is restricted; backup is configured; cron and queues are operational; the old server can be turned off after final verification.

Development of Two Specialized Websites for Selling Spare PartsGeneral Information It is necessary to develop two specialized websites: Spare parts for ATVs, UTVs, SSVs, and other similar equipment. Spare parts for special equipment. Existing company website: https://kiaparts.com.ua/ The new projects should not be copies of the existing website. A modern solution should be proposed with an emphasis on SEO, speed of operation, convenience for clients and managers, as well as the possibility of further development and scaling.Main Goal of the Project To create not just an online store, but a platform for selling spare parts that will: be well indexed by Google; attract organic traffic; be easy for managers to fill; support large product catalogs; be easily scalable in the future. For me, it is more important to achieve the correct architecture and foundation of the project than to have a large number of features in the first version.Project Architecture Two separate websites are needed for clients. At the same time, it is desirable that they be built on a single platform: one administrative panel; shared functionality; one or related databases; separate domains; separate content; the possibility of different designs and layouts for each project. That is, essentially two separate websites for the client, but one management system for the company. The advantage will be a modular architecture that will allow launching new projects on the same platform in the future.SEO (one of the main priorities) The main task of the website is not only to sell products but also to gain maximum organic traffic from Google. For each spare part, a separate product page with its own URL must be created. An example of an existing product page is attached, demonstrating the general principle of filling in SEO information. For each product, it should be possible to add: part number; OEM number; cross numbers; analogs; brand; name; alternative names; characteristics; photos; description; PDF files; list of applications; list of equipment models. The main goal: For one spare part to be able to receive traffic from dozens of different search queries: OEM number; cross number; analog; name; brand; equipment model.Important Regarding Data Structure I do not want managers to manually write large texts for each page. It is desirable to implement a structured data system: Product → OEM number → Cross numbers → Analogs → Applications → Equipment models → SEO page That is, the manager fills in the information once, and the system uses it for: SEO; search; interlinking; filters; analogs.Catalog and Search It is necessary to implement search: by number; by part number; by OEM number; by cross number; by name; by brand. Desirable: auto-suggestions; fast search; search for analogs; fast operation even with a large catalog.Import and Update of Products Mandatory: Excel import; CSV import; data export; bulk price updates; bulk stock updates; bulk description updates; bulk photo updates; bulk SEO data updates.Inventory Management It is necessary to implement: multiple warehouses; availability display; product reservation; stock synchronization. In the future, the ability to synchronize with the old main website and other company projects will be necessary.Security It is necessary to provide for: administrative panel protection; two-factor authentication; access rights segregation; user action log; protection against common attacks; API and integration protection.Backup It is necessary to implement: automatic database dumps; automatic file backups; photo backups; document backups; automatic saving of copies to the cloud (Google Drive, AWS, Backblaze, or similar services); the ability for quick recovery after a failure or hacking.Further Development In the first stage, the implementation of the functionality listed below is not mandatory. However, the architecture should allow for its further implementation without the need to create a new website. In the future, the following may be implemented: AI search in the catalog; AI generation of product descriptions; AI generation of SEO content; automatic search for analogs; integration with CRM; integration with suppliers via API; automation of manager work; sales analytics; B2B client cabinets; marketing tools. Therefore, it is important that the architecture is ready for further development.Examples of Websites Like in structure, logic, and convenience: Chrysler.com.ua Secoparts.net Comtac.parts RockAuto.com There is no need to copy the design of these websites. They are provided as examples of a convenient catalog structure, search, and information presentation.Platform The use of OpenCart, WordPress/WooCommerce, or other platforms is allowed. Main requirements: good SEO architecture; fast operation; scalability; availability of API; possibility of further development. Please justify the choice of platform and explain the prospects for project development on it.Budget Estimated budget for the first stage: 3,000 – 7,000 USD for the entire project (two websites on a single platform). The budget can be reviewed after discussing the architecture and implementation stages. I am ready to consider phased implementation, but it is preferable to implement part of it more urgently for launch. It is more important to achieve the correct architecture and quality foundation for further development than to have the maximum number of features in the first version.What I Expect from the Contractor proposal for architecture; platform recommendation; examples of similar works; estimated budget; estimated timelines; vision for further project development. Experience in creating catalogs of auto parts, stores with searches by OEM numbers and cross numbers, as well as projects with large product catalogs will be a big plus. Also, please add a brief description of how you see the SEO architecture of the project and how organic growth of the catalog will be ensured. Photos are attached for a simple example of a page for organic search.