One-sided php site by sample of the existing site

Technical TaskProject Setting up a product feed for Google Merchant Center for use in Meta Commerce Manager (Facebook and Instagram).Goal Create a single XML feed that meets the requirements of Google Merchant Center and can be used for importing products into Meta Commerce Manager without additional modifications.Main RequirementsFeed Format XML RSS 2.0 (Google Merchant Feed). UTF-8 encoding. Access via a permanent HTTPS link. Automatic updates at least once a day.Mandatory Fields For each product, the following must be provided: id title description link image_link availability price brand condition gtin (if available) mpn (if GTIN is not available) google_product_category (if possible) product_type sale_price (if a promotion is active) additional_image_link (if available) shipping (if necessary) item_group_id (for variable products) color size gender (for clothing) age_group (for clothing)Content RequirementsProduct Title Up to 150 characters. No HTML. No promotional phrases. Must include the main characteristics of the product.Description Up to 5000 characters. No HTML. Unique. Contains product characteristics.Photos HTTPS. Minimum 500×500 px. No watermarks. One main photo and, if possible, additional ones.Price Format:999.00 UAH The price in the feed must match the price on the website.Availability Allowed values: in_stock out_of_stock preorder backorderVariable Products If a product has multiple colors or sizes: same item_group_id; different id; separate values for color and size.Links For each product: the product page must open without errors; use HTTPS; there should be no redirects to other products.Updates automatic feed generation; updates at least once every 24 hours; after a price or stock change, updates must be reflected in the feed automatically.Compatibility with Meta The feed must import correctly into Meta Commerce Manager without errors. Google Merchant fields must be compatible with Meta Catalog requirements.Result After the work is completed, the following must be provided: link to the XML feed; example of one product in the feed; confirmation of passing Google Merchant Center validation; confirmation of successful catalog import into Meta Commerce Manager.

We are looking for a PHP Backend Developer to refine and clone gaming projects. In the first stage, it is necessary to complete the existing project and adapt it to the technical requirements. After successful implementation, a series of similar tasks and long-term cooperation is planned. Confident experience in PHP backend development and experience with gaming projects are required. When responding, please attach examples of completed projects and briefly describe your role. Payment for task completion is $100, the price for subsequent development from scratch is negotiable.

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.