<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Artem (tema.name)</title>
    <description>The latest articles on DEV Community by Artem (tema.name) (@temaname).</description>
    <link>https://dev.to/temaname</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4242569%2Fb6d5b191-9548-421c-8194-fbda0eddd584.png</url>
      <title>DEV Community: Artem (tema.name)</title>
      <link>https://dev.to/temaname</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/temaname"/>
    <language>en</language>
    <item>
      <title>Accepting BLIK and Przelewy24 payments in a Telegram bot: how it works</title>
      <dc:creator>Artem (tema.name)</dc:creator>
      <pubDate>Sun, 15 Nov 2026 19:20:03 +0000</pubDate>
      <link>https://dev.to/temaname/accepting-blik-and-przelewy24-payments-in-a-telegram-bot-how-it-works-185d</link>
      <guid>https://dev.to/temaname/accepting-blik-and-przelewy24-payments-in-a-telegram-bot-how-it-works-185d</guid>
      <description>&lt;p&gt;In Poland, most people pay online with BLIK: a six-digit code from the banking app. If your Telegram bot sells something to Polish customers (bookings, courses, products), card-only payments lose a lot of buyers. Here is how BLIK fits into a bot, and what I watch out for.&lt;/p&gt;

&lt;h2&gt;
  
  
  Option 1: Telegram Payments with a provider
&lt;/h2&gt;

&lt;p&gt;Telegram has a built-in payments API. You connect a payment provider in BotFather and send an invoice with &lt;code&gt;sendInvoice&lt;/code&gt;. The user pays inside Telegram.&lt;/p&gt;

&lt;p&gt;The catch: you depend on which providers Telegram supports for your country and currency, and BLIK is not always available there. Check the current provider list before you build on it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Option 2: payment link from Przelewy24
&lt;/h2&gt;

&lt;p&gt;The more flexible way, and the one I use most often:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The bot collects the order (service, date, product, quantity).&lt;/li&gt;
&lt;li&gt;Your backend creates a transaction in Przelewy24 through their REST API and gets a payment link.&lt;/li&gt;
&lt;li&gt;The bot sends a button with that link.&lt;/li&gt;
&lt;li&gt;The customer chooses BLIK (or a bank transfer, or a card) on the Przelewy24 page and pays.&lt;/li&gt;
&lt;li&gt;Przelewy24 calls your notification URL. Your backend &lt;strong&gt;verifies&lt;/strong&gt; the transaction through the API.&lt;/li&gt;
&lt;li&gt;Only after verification does the bot confirm the order and notify you.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Przelewy24 supports BLIK, quick bank transfers and cards on one payment page, so you do not have to integrate each method separately.&lt;/p&gt;

&lt;h2&gt;
  
  
  Things that break in real projects
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Trusting the redirect.&lt;/strong&gt; The customer coming back to the "success" page does not mean the money arrived. Always confirm through the server notification and the verify call.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Amounts in grosze.&lt;/strong&gt; Przelewy24 expects the amount in the smallest unit: 49.99 zł is &lt;code&gt;4999&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Duplicate notifications.&lt;/strong&gt; The notification can arrive more than once. Make the handler idempotent: one order, one confirmation.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Test vs production.&lt;/strong&gt; Przelewy24 has a sandbox with separate credentials. Keep them in configuration, not in code.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Invoices.&lt;/strong&gt; If you are a business, the customer may need a receipt or invoice. Decide early where it is generated.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Hosting the bot
&lt;/h2&gt;

&lt;p&gt;A webhook-based bot needs an HTTPS endpoint that is always online. A small VPS or a serverless function is enough. Store orders in a database, not in memory, so a restart does not lose payments.&lt;/p&gt;

&lt;h2&gt;
  
  
  Is it worth it?
&lt;/h2&gt;

&lt;p&gt;For Polish customers, yes: a BLIK payment takes about ten seconds and needs no card details. Bots that switch from "pay by bank transfer and send a screenshot" to BLIK usually get fewer abandoned orders and less manual checking.&lt;/p&gt;




&lt;p&gt;I wrote a longer version with costs: &lt;a href="https://tema.name/en/blog/telegram-bot-payments-poland-blik-przelewy24-2026.html" rel="noopener noreferrer"&gt;Telegram bot payments in Poland: BLIK and Przelewy24&lt;/a&gt;. If you need such a bot built: &lt;a href="https://tema.name/en/services/telegram-bot-blik-przelewy24.html" rel="noopener noreferrer"&gt;Telegram bot with BLIK and Przelewy24&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>telegram</category>
      <category>payments</category>
      <category>python</category>
      <category>webdev</category>
    </item>
    <item>
      <title>WordPress or WooCommerce not sending emails? Fix it in this order</title>
      <dc:creator>Artem (tema.name)</dc:creator>
      <pubDate>Sun, 15 Nov 2026 19:19:03 +0000</pubDate>
      <link>https://dev.to/temaname/wordpress-or-woocommerce-not-sending-emails-fix-it-in-this-order-1177</link>
      <guid>https://dev.to/temaname/wordpress-or-woocommerce-not-sending-emails-fix-it-in-this-order-1177</guid>
      <description>&lt;p&gt;Order confirmations do not arrive, contact form messages disappear, password reset emails end up in spam. This is one of the most common WordPress problems, and in most cases the reason is the same: WordPress sends mail through PHP &lt;code&gt;mail()&lt;/code&gt; from a server that mail providers do not trust.&lt;/p&gt;

&lt;p&gt;Here is the order I check things on client sites.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Find out if mail is sent at all
&lt;/h2&gt;

&lt;p&gt;Install a mail logging plugin (WP Mail Logging, or the log in your SMTP plugin) and trigger a test: a contact form message or a WooCommerce test order.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Nothing in the log&lt;/strong&gt;: the form or plugin never called &lt;code&gt;wp_mail()&lt;/code&gt;. Check the form settings and the WooCommerce email settings (each email type can be disabled).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;In the log, but not delivered&lt;/strong&gt;: WordPress did its part, the problem is delivery. Continue below.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  2. Stop using PHP mail()
&lt;/h2&gt;

&lt;p&gt;Shared hosting servers send mail from an IP that also sends mail for hundreds of other sites. Gmail and Outlook treat it with suspicion. Send through a real mailbox instead:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;your domain mailbox (the SMTP server from your hosting or Google Workspace / Microsoft 365)&lt;/li&gt;
&lt;li&gt;or a transactional service (Brevo, Postmark, Amazon SES, Mailgun)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Use an SMTP plugin (WP Mail SMTP, FluentSMTP, Post SMTP) and send a test email from its settings page.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. The "From" address must match the domain
&lt;/h2&gt;

&lt;p&gt;A common mistake: the site sends as &lt;code&gt;noreply@example.com&lt;/code&gt;, but SMTP logs in as &lt;code&gt;someone@gmail.com&lt;/code&gt;. Providers see a mismatch and reject or hide the message. Send from an address on your own domain and authenticate as that address.&lt;/p&gt;

&lt;p&gt;Contact forms should use the visitor's email in &lt;strong&gt;Reply-To&lt;/strong&gt;, not in From.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. SPF, DKIM, DMARC
&lt;/h2&gt;

&lt;p&gt;Without these DNS records, even correct SMTP mail lands in spam.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;SPF&lt;/strong&gt;: lists the servers allowed to send for your domain. Only one SPF record per domain.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;DKIM&lt;/strong&gt;: a signature your mail service gives you as a DNS record.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;DMARC&lt;/strong&gt;: tells receivers what to do with mail that fails the checks. Start with &lt;code&gt;p=none&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Send a test to a checker like mail-tester.com and fix everything it marks red.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. WooCommerce specifics
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Check WooCommerce &amp;gt; Settings &amp;gt; Emails: every email type has its own on/off switch and recipient.&lt;/li&gt;
&lt;li&gt;If emails stopped after an update, look for a plugin that overrides email templates.&lt;/li&gt;
&lt;li&gt;Order emails are sent in the background on some setups. If WP-Cron does not run (low traffic or disabled cron), emails are delayed. Set up a real server cron.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  6. Test like a customer
&lt;/h2&gt;

&lt;p&gt;Place a real test order with a Gmail and an Outlook address. Check inbox, spam and promotions. Only then call it fixed.&lt;/p&gt;




&lt;p&gt;If you would rather hand it over: I set up SMTP, DNS records and test delivery for WordPress and WooCommerce sites. Details: &lt;a href="https://tema.name/en/services/wordpress-woocommerce-email-setup.html" rel="noopener noreferrer"&gt;WordPress and WooCommerce email setup&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>wordpress</category>
      <category>woocommerce</category>
      <category>email</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Your site redirects to a casino: how to find and remove the injected code</title>
      <dc:creator>Artem (tema.name)</dc:creator>
      <pubDate>Fri, 13 Nov 2026 09:12:26 +0000</pubDate>
      <link>https://dev.to/temaname/your-site-redirects-to-a-casino-how-to-find-and-remove-the-injected-code-1fkf</link>
      <guid>https://dev.to/temaname/your-site-redirects-to-a-casino-how-to-find-and-remove-the-injected-code-1fkf</guid>
      <description>&lt;p&gt;A client writes: "People say my site opens a casino. I open it and everything is fine." This is the most common hack I clean up on WordPress and Joomla sites. Here is how it works and how to remove it properly.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why the owner does not see it
&lt;/h2&gt;

&lt;p&gt;The injected code is selective. Typical conditions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;the visitor came from Google or another search engine&lt;/li&gt;
&lt;li&gt;the visitor is on a phone&lt;/li&gt;
&lt;li&gt;it is the first visit from this IP or without a cookie&lt;/li&gt;
&lt;li&gt;the visitor is not logged in&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The owner types the address directly, is logged in and has visited before, so the site looks normal. To reproduce the redirect, open a search result for your site in a private window on a phone, or send a request with a mobile user agent and a Google referrer:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl -sIL -A &lt;span class="s2"&gt;"Mozilla/5.0 (Linux; Android 14) Mobile"&lt;/span&gt; -e &lt;span class="s2"&gt;"https://www.google.com/"&lt;/span&gt; https://example.com/ &lt;span class="o"&gt;|&lt;/span&gt; grep -i -E &lt;span class="s2"&gt;"^HTTP|^location"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If you see a &lt;code&gt;location:&lt;/code&gt; header pointing to a domain you do not know, the redirect is real.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where the code usually lives
&lt;/h2&gt;

&lt;p&gt;Check these places in this order.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. &lt;code&gt;.htaccess&lt;/code&gt;&lt;/strong&gt; in the site root and in every subfolder. Look for &lt;code&gt;RewriteCond %{HTTP_REFERER}&lt;/code&gt; or &lt;code&gt;%{HTTP_USER_AGENT}&lt;/code&gt; rules that you did not write.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Entry files&lt;/strong&gt;: &lt;code&gt;index.php&lt;/code&gt;, &lt;code&gt;wp-config.php&lt;/code&gt;, &lt;code&gt;wp-blog-header.php&lt;/code&gt;, &lt;code&gt;wp-load.php&lt;/code&gt;, &lt;code&gt;configuration.php&lt;/code&gt; and &lt;code&gt;includes/defines.php&lt;/code&gt; in Joomla. An injected block is often at the very top of the file, sometimes after hundreds of spaces so you do not see it without scrolling right.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Theme and template files&lt;/strong&gt;: &lt;code&gt;functions.php&lt;/code&gt;, &lt;code&gt;header.php&lt;/code&gt;, &lt;code&gt;footer.php&lt;/code&gt;, the template &lt;code&gt;index.php&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Fake plugins and must-use plugins&lt;/strong&gt;: &lt;code&gt;wp-content/mu-plugins/&lt;/code&gt; is loaded automatically and does not appear in the normal plugin list. Also look for plugin folders with generic names you did not install.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5. The database&lt;/strong&gt;: in WordPress, the &lt;code&gt;wp_options&lt;/code&gt; table (&lt;code&gt;siteurl&lt;/code&gt;, &lt;code&gt;home&lt;/code&gt;, and rows with long encoded values) and &lt;code&gt;wp_posts&lt;/code&gt; with &lt;code&gt;&amp;lt;script&amp;gt;&lt;/code&gt; tags inside content. In Joomla, custom HTML modules and the template parameters.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;6. JavaScript files&lt;/strong&gt;: a line appended to jQuery or to the theme script that loads code from another domain.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;7. Uploads&lt;/strong&gt;: PHP files in &lt;code&gt;wp-content/uploads/&lt;/code&gt; or Joomla &lt;code&gt;images/&lt;/code&gt; and &lt;code&gt;media/&lt;/code&gt;. There should be none.&lt;/p&gt;

&lt;h2&gt;
  
  
  Useful searches
&lt;/h2&gt;

&lt;p&gt;Files changed in the last two weeks:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;find . -type f -name &lt;span class="s2"&gt;"*.php"&lt;/span&gt; -mtime -14 -not -path &lt;span class="s2"&gt;"./wp-content/cache/*"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;PHP files where they should not be:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;find wp-content/uploads -type f -name &lt;span class="s2"&gt;"*.php"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Typical obfuscation:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;grep -rlE &lt;span class="s2"&gt;"eval\(|base64_decode\(|gzinflate\(|str_rot13\(|fromCharCode"&lt;/span&gt; --include=&lt;span class="s2"&gt;"*.php"&lt;/span&gt; --include=&lt;span class="s2"&gt;"*.js"&lt;/span&gt; .
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;These functions are also used by honest code, so read every match before deleting anything. Modification dates can be faked too: treat them as a hint, not as proof.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why it comes back
&lt;/h2&gt;

&lt;p&gt;If you delete the redirect and it returns in a day, something restores it. Look for:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;a backdoor file (a small PHP script that accepts commands)&lt;/li&gt;
&lt;li&gt;an unknown administrator account&lt;/li&gt;
&lt;li&gt;a scheduled task: &lt;code&gt;crontab -l&lt;/code&gt; on the server and the WP-Cron list&lt;/li&gt;
&lt;li&gt;a still running malicious PHP process that rewrites files (restart PHP after cleaning)&lt;/li&gt;
&lt;li&gt;another infected site in the same hosting account&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Cleaning in the right order
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Make a full backup of the infected site. You may need it to recover content.&lt;/li&gt;
&lt;li&gt;Close the site for maintenance or restrict access by IP.&lt;/li&gt;
&lt;li&gt;Replace the core with a clean copy of the same version. For WordPress: delete &lt;code&gt;wp-admin&lt;/code&gt; and &lt;code&gt;wp-includes&lt;/code&gt; and upload fresh ones. Do the same for Joomla core folders.&lt;/li&gt;
&lt;li&gt;Reinstall every plugin, extension and theme from the original source. Do not "clean" them by hand if a clean copy exists.&lt;/li&gt;
&lt;li&gt;Review what is left by hand: &lt;code&gt;wp-content&lt;/code&gt;, uploads, &lt;code&gt;.htaccess&lt;/code&gt;, config files.&lt;/li&gt;
&lt;li&gt;Clean the database.&lt;/li&gt;
&lt;li&gt;Remove unknown users. Change every password: admin, database, FTP or SSH, hosting panel. Replace the WordPress salts so all sessions end.&lt;/li&gt;
&lt;li&gt;Update everything and remove what you do not use.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Close the hole
&lt;/h2&gt;

&lt;p&gt;Cleaning without finding the entry point is half the job. The usual causes are an outdated plugin or extension, a nulled theme, a weak admin password, or a neighbour site on the same account. Check the access log for the first POST request to the backdoor file: the date tells you which backup is clean and which vulnerability was used.&lt;/p&gt;

&lt;p&gt;Then: disable PHP execution in upload folders, turn off file editing in the admin panel, set up automatic backups stored outside the server.&lt;/p&gt;

&lt;h2&gt;
  
  
  After cleaning
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;In Google Search Console, open &lt;strong&gt;Security issues&lt;/strong&gt; and request a review if there is a warning.&lt;/li&gt;
&lt;li&gt;Check that the sitemap and &lt;code&gt;robots.txt&lt;/code&gt; are your own.&lt;/li&gt;
&lt;li&gt;Look at the indexed pages with &lt;code&gt;site:example.com&lt;/code&gt;: spam pages created by the attacker should return 404 or 410.&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;If you do not want to do this yourself, I clean hacked WordPress and Joomla sites and close the entry point: &lt;a href="https://tema.name/en/services/website-hack-recovery.html" rel="noopener noreferrer"&gt;website hack recovery&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>wordpress</category>
      <category>security</category>
      <category>webdev</category>
      <category>php</category>
    </item>
    <item>
      <title>Upgrading Joomla 3 to Joomla 6: the order that does not break the site</title>
      <dc:creator>Artem (tema.name)</dc:creator>
      <pubDate>Fri, 13 Nov 2026 09:11:19 +0000</pubDate>
      <link>https://dev.to/temaname/upgrading-joomla-3-to-joomla-6-the-order-that-does-not-break-the-site-19pi</link>
      <guid>https://dev.to/temaname/upgrading-joomla-3-to-joomla-6-the-order-that-does-not-break-the-site-19pi</guid>
      <description>&lt;p&gt;Many Joomla 3 sites are still online in 2026. They work, so nobody touches them, and then the host switches off old PHP versions and the site goes down on a Monday morning.&lt;/p&gt;

&lt;p&gt;There is no direct jump from Joomla 3 to Joomla 6. You go through every major version. Here is the order I use on client sites, and the places where upgrades usually fail.&lt;/p&gt;

&lt;h2&gt;
  
  
  The path
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Joomla 3.10.x  -&amp;gt;  4.4.x  -&amp;gt;  5.4.x  -&amp;gt;  6.x
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Each arrow is a separate upgrade with its own checks. Joomla 3.10, 4.4 and 5.4 are "bridge" releases: they exist to prepare the site for the next major version.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 0. Work on a copy
&lt;/h2&gt;

&lt;p&gt;Never upgrade the live site. Make a full backup (files and database), restore it on a staging subdomain or a local server, and close the copy from search engines. The live site keeps working while you break things on the copy.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1. Audit extensions and the template
&lt;/h2&gt;

&lt;p&gt;This is where most of the work is. For every installed extension, write down:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Is there a version for Joomla 4, 5 and 6?&lt;/li&gt;
&lt;li&gt;Is it still maintained at all?&lt;/li&gt;
&lt;li&gt;Do you actually use it?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A typical Joomla 3 site has 30 to 60 extensions and uses a third of them. Uninstall what you do not need &lt;strong&gt;before&lt;/strong&gt; the upgrade. Every abandoned plugin is a possible fatal error later.&lt;/p&gt;

&lt;p&gt;The template is the second risk. Most Joomla 3 templates do not run on Joomla 4 or newer. Check whether the vendor has a new version. If not, plan to rebuild the design on a current template or framework.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2. Joomla 3.10 and the pre-update check
&lt;/h2&gt;

&lt;p&gt;Update to the latest 3.10.x first. It adds the &lt;strong&gt;Pre-Update Check&lt;/strong&gt;: a screen that shows which extensions are not compatible with Joomla 4 and whether your server meets the requirements.&lt;/p&gt;

&lt;p&gt;Do not continue until that list is clean. Update, replace or remove everything it marks.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3. PHP and the database
&lt;/h2&gt;

&lt;p&gt;Requirements grow with every major version. Joomla 6 needs PHP 8.3 or newer and a current database server (MySQL 8.0.13+, MariaDB 10.6+ or PostgreSQL 14+).&lt;/p&gt;

&lt;p&gt;The trap: Joomla 3.10 does not officially support the newest PHP versions, and Joomla 6 does not run on the old ones. So you switch PHP in steps, together with the Joomla version, and test after each switch. Check which versions your host offers before you start.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4. Upgrade to 4.4, then test
&lt;/h2&gt;

&lt;p&gt;Switch the update channel to "Joomla Next" and upgrade to 4.4.x. Then check:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;frontend pages and menus&lt;/li&gt;
&lt;li&gt;login and user registration&lt;/li&gt;
&lt;li&gt;contact forms and email&lt;/li&gt;
&lt;li&gt;the admin panel, especially custom fields and modules&lt;/li&gt;
&lt;li&gt;the error log&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Joomla 4 removed a lot of old API. Template overrides copied from Joomla 3 are a classic source of white pages. If a page is broken, rename the &lt;code&gt;html&lt;/code&gt; folder of the template and see if the page comes back.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 5. Upgrade to 5.4
&lt;/h2&gt;

&lt;p&gt;Joomla 5 ships with the &lt;strong&gt;Behaviour - Backward Compatibility&lt;/strong&gt; plugin. It keeps old class names working. Leave it enabled during the upgrade, then try to switch it off on the copy: if the site survives, your extensions are ready for the next step.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 6. Upgrade to 6
&lt;/h2&gt;

&lt;p&gt;Update all extensions again, read the pre-update check again, then upgrade. Joomla 6 has its own compatibility plugin for code written for Joomla 5. The same rule applies: if an extension only works with the compatibility plugin, it will break in the next major version, so ask the vendor about an update.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 7. URLs and SEO
&lt;/h2&gt;

&lt;p&gt;An upgrade should not change your URLs, but a new template, a new menu structure or a replaced SEF extension can. Before going live:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;crawl the old site and the new copy and compare the URL lists&lt;/li&gt;
&lt;li&gt;add 301 redirects for every address that changed&lt;/li&gt;
&lt;li&gt;compare titles, meta descriptions and canonical tags&lt;/li&gt;
&lt;li&gt;check &lt;code&gt;robots.txt&lt;/code&gt; and the sitemap&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Step 8. Go live
&lt;/h2&gt;

&lt;p&gt;Pick a quiet hour. Take a fresh backup of the live site, move the upgraded copy into place, import content that changed during the work (new articles, orders, users), clear the cache and test again. Keep the old backup for at least a month.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where upgrades usually fail
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;An abandoned extension with no Joomla 4+ version.&lt;/li&gt;
&lt;li&gt;A template that was never updated.&lt;/li&gt;
&lt;li&gt;Template overrides from Joomla 3.&lt;/li&gt;
&lt;li&gt;PHP switched too early or too late.&lt;/li&gt;
&lt;li&gt;Custom code written directly into core files.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;None of these is a reason to stay on Joomla 3. They are reasons to do the upgrade on a copy and in the right order.&lt;/p&gt;




&lt;p&gt;I do these upgrades for clients: audit, staging copy, upgrade to Joomla 6, redirects and testing. Details and prices: &lt;a href="https://tema.name/en/services/joomla-upgrade-migration.html" rel="noopener noreferrer"&gt;Joomla upgrade and migration&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>joomla</category>
      <category>php</category>
      <category>webdev</category>
      <category>tutorial</category>
    </item>
  </channel>
</rss>
