[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-should-philippine-teams-upgrade-to-laravel-13":3,"blog-nav-should-philippine-teams-upgrade-to-laravel-13":27},{"slug":4,"title":5,"description":6,"body":7,"category":8,"readTime":9,"tags":10,"coverImage":14,"coverImageAlt":15,"heroImage":16,"heroImageAlt":15,"metaTitle":17,"metaDescription":18,"ogImage":19,"noindex":20,"published":21,"publishAt":22,"sortOrder":23,"updatedAt":22,"status":24,"path":25,"bodyHtml":26},"should-philippine-teams-upgrade-to-laravel-13","Should Philippine teams upgrade to Laravel 13 — or wait?","Laravel 12 bug fixes ended 13 August 2026. Here is when to move to Laravel 13, when security-only is enough, and what PHP 8.3 changes for Philippine production apps.","Laravel 12’s bug-fix window closed on **13 August 2026**. Security patches continue until February 2027, but new framework bugs are now your problem. The practical question for Philippine teams is not “is Laravel 13 shiny?” — it is **upgrade now, or wait with a written plan**.\n\nThis is the decision we walk through with clients who already have a production Laravel app — not a greenfield tutorial.\n\n## What the calendar actually means\n\nLaravel’s current policy is uniform: **18 months of bug fixes, two years of security**. There is no LTS escape hatch.\n\n| Version | Released | Bug fixes | Security until | Status in September 2026 |\n|---------|----------|-----------|----------------|--------------------------|\n| Laravel 11 | Mar 2024 | Ended Sep 2025 | Ended Mar 2026 | Uncovered — move |\n| Laravel 12 | Feb 2025 | Ended 13 Aug 2026 | Feb 2027 | Security only |\n| Laravel 13 | 17 Mar 2026 | Through Q3 2027 | Mar 2028 | Current major |\n\nLaravel 13 needs **PHP 8.3 or newer**. If you are still on PHP 8.2 — common on older shared and some VPS images — that is the first job, before you touch `composer.json`.\n\nNew work should start on 13 unless a package or host blocks you. Laravel 11 or older is not “a little behind.” It is out of security support.\n\n## Upgrade now if these are true\n\nMove this quarter when:\n\n- You are already on **PHP 8.3+** in staging and production\n- Composer dependencies have Laravel 13 releases (or clear forks)\n- You have a **test suite** that exercises checkout, auth, queues, and the two or three flows that make money\n- You want the longer security window and first-party AI primitives without rushing them into production on day one\n\nOfficial notes describe Laravel 13 as a **small application-code upgrade** for typical apps — CSRF middleware renamed (`VerifyCsrfToken` → `PreventRequestForgery`), stricter cache deserialization defaults, prefix\u002Fcookie naming to pin if you relied on framework defaults. Most of the pain is **PHP version and stale packages**, not rewriting controllers.\n\nThat matches how we treat framework work generally: change the runtime in isolation, then the framework, then features. Same discipline as [how we build scalable web applications](\u002Fblog\u002Fhow-we-build-scalable-web-applications).\n\n## Wait (briefly) if these are true\n\nWaiting is legitimate when it is **time-boxed**, not vague:\n\n- Production is still on **PHP 8.2** and the host change is a separate ops project\n- A critical package has no Laravel 13 release and no maintained alternative\n- You have **no automated tests** around payments, bookings, or inventory — upgrade-then-hope is how you get a quiet production incident\n- You are mid-feature freeze for a launch week\n\nLaravel 12 still gets **security fixes until 24 February 2027**. That is a runway, not a destination. Write the upgrade date. Do not treat “we will get to it” as a plan.\n\nIf you are on 11 or older, waiting is not a strategy. Budget the jump.\n\n## A sane upgrade sequence\n\n1. **Inventory** — PHP version, first-party packages, paid modules, custom middleware that names `VerifyCsrfToken`\n2. **PHP first** — 8.3+ on local, CI, and production, proven independently\n3. **Composer** — `laravel\u002Fframework ^13.0` and matching first-party constraints on a branch\n4. **Config review** — cache `serializable_classes`, explicit `CACHE_PREFIX` \u002F session cookie if you need old keys\n5. **Tests + staging** — money paths, webhooks, queues, Filament\u002FNova\u002Fadmin if you have them\n6. **Production** — deploy, flush cache, watch logs for a week\n\nSkip “upgrade and add AI in the same release.” The [Laravel AI SDK](\u002Fblog\u002Flaravel-13-ai-sdk-philippine-business-apps) is a product conversation. This article is a **maintenance conversation**.\n\n## What we will not pretend\n\n- Upgrading does not magically speed up a plugin-shaped WordPress leftover. If you are still deciding the stack, read [Laravel vs WordPress for business websites](\u002Fblog\u002Flaravel-vs-wordpress-for-business-websites) first.\n- A weekend composer bump without staging is not “agile.” It is unpaid incident response.\n- You do not need to adopt every Laravel 13 headline feature to justify the move. **Supported PHP + supported framework** is enough reason.\n\n## Straight next step\n\nIf you run a Philippine business system on Laravel 12 (or older) and want a grounded upgrade path — what blocks you, what can wait, what we would do in which order — [send us the stack notes](\u002Fcontact). We will be direct about “this week,” “this quarter,” and “do not touch until PHP is sorted.”","Engineering",7,[11,12,13],"Laravel","Upgrades","Philippines","\u002Fimages\u002Fjournal\u002Fshould-philippine-teams-upgrade-to-laravel-13-cover.webp?v=20260730u","Diagram of the Laravel 12 to Laravel 13 upgrade path for Philippine production apps","\u002Fimages\u002Fjournal\u002Fshould-philippine-teams-upgrade-to-laravel-13-hero.webp?v=20260730u","Upgrade to Laravel 13? Philippine Teams | PrimeCode","Should Philippine teams upgrade to Laravel 13 after Laravel 12 bug fixes ended 13 Aug 2026 — now vs wait, PHP 8.3, and a sane sequence.","\u002Fimages\u002Fjournal\u002Fshould-philippine-teams-upgrade-to-laravel-13-og.webp?v=20260730u",false,true,"2026-09-02T01:00:00.000Z",33,"live","\u002Fblog\u002Fshould-philippine-teams-upgrade-to-laravel-13","\u003Cp>Laravel 12’s bug-fix window closed on \u003Cstrong>13 August 2026\u003C\u002Fstrong>. Security patches continue until February 2027, but new framework bugs are now your problem. The practical question for Philippine teams is not “is Laravel 13 shiny?” — it is \u003Cstrong>upgrade now, or wait with a written plan\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>This is the decision we walk through with clients who already have a production Laravel app — not a greenfield tutorial.\u003C\u002Fp>\n\u003Ch2>What the calendar actually means\u003C\u002Fh2>\n\u003Cp>Laravel’s current policy is uniform: \u003Cstrong>18 months of bug fixes, two years of security\u003C\u002Fstrong>. There is no LTS escape hatch.\u003C\u002Fp>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Version\u003C\u002Fth>\n\u003Cth>Released\u003C\u002Fth>\n\u003Cth>Bug fixes\u003C\u002Fth>\n\u003Cth>Security until\u003C\u002Fth>\n\u003Cth>Status in September 2026\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Laravel 11\u003C\u002Ftd>\n\u003Ctd>Mar 2024\u003C\u002Ftd>\n\u003Ctd>Ended Sep 2025\u003C\u002Ftd>\n\u003Ctd>Ended Mar 2026\u003C\u002Ftd>\n\u003Ctd>Uncovered — move\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Laravel 12\u003C\u002Ftd>\n\u003Ctd>Feb 2025\u003C\u002Ftd>\n\u003Ctd>Ended 13 Aug 2026\u003C\u002Ftd>\n\u003Ctd>Feb 2027\u003C\u002Ftd>\n\u003Ctd>Security only\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Laravel 13\u003C\u002Ftd>\n\u003Ctd>17 Mar 2026\u003C\u002Ftd>\n\u003Ctd>Through Q3 2027\u003C\u002Ftd>\n\u003Ctd>Mar 2028\u003C\u002Ftd>\n\u003Ctd>Current major\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\n\u003Cp>Laravel 13 needs \u003Cstrong>PHP 8.3 or newer\u003C\u002Fstrong>. If you are still on PHP 8.2 — common on older shared and some VPS images — that is the first job, before you touch \u003Ccode>composer.json\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>New work should start on 13 unless a package or host blocks you. Laravel 11 or older is not “a little behind.” It is out of security support.\u003C\u002Fp>\n\u003Ch2>Upgrade now if these are true\u003C\u002Fh2>\n\u003Cp>Move this quarter when:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>You are already on \u003Cstrong>PHP 8.3+\u003C\u002Fstrong> in staging and production\u003C\u002Fli>\n\u003Cli>Composer dependencies have Laravel 13 releases (or clear forks)\u003C\u002Fli>\n\u003Cli>You have a \u003Cstrong>test suite\u003C\u002Fstrong> that exercises checkout, auth, queues, and the two or three flows that make money\u003C\u002Fli>\n\u003Cli>You want the longer security window and first-party AI primitives without rushing them into production on day one\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Official notes describe Laravel 13 as a \u003Cstrong>small application-code upgrade\u003C\u002Fstrong> for typical apps — CSRF middleware renamed (\u003Ccode>VerifyCsrfToken\u003C\u002Fcode> → \u003Ccode>PreventRequestForgery\u003C\u002Fcode>), stricter cache deserialization defaults, prefix\u002Fcookie naming to pin if you relied on framework defaults. Most of the pain is \u003Cstrong>PHP version and stale packages\u003C\u002Fstrong>, not rewriting controllers.\u003C\u002Fp>\n\u003Cp>That matches how we treat framework work generally: change the runtime in isolation, then the framework, then features. Same discipline as \u003Ca href=\"\u002Fblog\u002Fhow-we-build-scalable-web-applications\" rel=\"noopener noreferrer\">how we build scalable web applications\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2>Wait (briefly) if these are true\u003C\u002Fh2>\n\u003Cp>Waiting is legitimate when it is \u003Cstrong>time-boxed\u003C\u002Fstrong>, not vague:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Production is still on \u003Cstrong>PHP 8.2\u003C\u002Fstrong> and the host change is a separate ops project\u003C\u002Fli>\n\u003Cli>A critical package has no Laravel 13 release and no maintained alternative\u003C\u002Fli>\n\u003Cli>You have \u003Cstrong>no automated tests\u003C\u002Fstrong> around payments, bookings, or inventory — upgrade-then-hope is how you get a quiet production incident\u003C\u002Fli>\n\u003Cli>You are mid-feature freeze for a launch week\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Laravel 12 still gets \u003Cstrong>security fixes until 24 February 2027\u003C\u002Fstrong>. That is a runway, not a destination. Write the upgrade date. Do not treat “we will get to it” as a plan.\u003C\u002Fp>\n\u003Cp>If you are on 11 or older, waiting is not a strategy. Budget the jump.\u003C\u002Fp>\n\u003Ch2>A sane upgrade sequence\u003C\u002Fh2>\n\u003Col>\n\u003Cli>\u003Cstrong>Inventory\u003C\u002Fstrong> — PHP version, first-party packages, paid modules, custom middleware that names \u003Ccode>VerifyCsrfToken\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>PHP first\u003C\u002Fstrong> — 8.3+ on local, CI, and production, proven independently\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Composer\u003C\u002Fstrong> — \u003Ccode>laravel\u002Fframework ^13.0\u003C\u002Fcode> and matching first-party constraints on a branch\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Config review\u003C\u002Fstrong> — cache \u003Ccode>serializable_classes\u003C\u002Fcode>, explicit \u003Ccode>CACHE_PREFIX\u003C\u002Fcode> \u002F session cookie if you need old keys\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Tests + staging\u003C\u002Fstrong> — money paths, webhooks, queues, Filament\u002FNova\u002Fadmin if you have them\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Production\u003C\u002Fstrong> — deploy, flush cache, watch logs for a week\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Skip “upgrade and add AI in the same release.” The \u003Ca href=\"\u002Fblog\u002Flaravel-13-ai-sdk-philippine-business-apps\" rel=\"noopener noreferrer\">Laravel AI SDK\u003C\u002Fa> is a product conversation. This article is a \u003Cstrong>maintenance conversation\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Ch2>What we will not pretend\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Upgrading does not magically speed up a plugin-shaped WordPress leftover. If you are still deciding the stack, read \u003Ca href=\"\u002Fblog\u002Flaravel-vs-wordpress-for-business-websites\" rel=\"noopener noreferrer\">Laravel vs WordPress for business websites\u003C\u002Fa> first.\u003C\u002Fli>\n\u003Cli>A weekend composer bump without staging is not “agile.” It is unpaid incident response.\u003C\u002Fli>\n\u003Cli>You do not need to adopt every Laravel 13 headline feature to justify the move. \u003Cstrong>Supported PHP + supported framework\u003C\u002Fstrong> is enough reason.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Straight next step\u003C\u002Fh2>\n\u003Cp>If you run a Philippine business system on Laravel 12 (or older) and want a grounded upgrade path — what blocks you, what can wait, what we would do in which order — \u003Ca href=\"\u002Fcontact\" rel=\"noopener noreferrer\">send us the stack notes\u003C\u002Fa>. We will be direct about “this week,” “this quarter,” and “do not touch until PHP is sorted.”\u003C\u002Fp>\n",{"prev":28,"next":45,"related":61},{"slug":29,"title":30,"description":31,"category":32,"readTime":33,"tags":34,"coverImage":36,"coverImageAlt":37,"heroImage":38,"heroImageAlt":37,"metaTitle":39,"metaDescription":40,"ogImage":41,"noindex":20,"published":21,"publishAt":42,"sortOrder":43,"updatedAt":42,"status":24,"path":44},"cybersecurity-trends-philippine-smes-2026","Cybersecurity trends for Philippine SMEs in 2026: what actually matters","Ransomware pitches and “AI security” bundles are everywhere. Here are the controls that matter for Philippine SMEs — phishing, access, backups, and vendor risk — without enterprise theater.","Trends",6,[32,35,13],"Security","\u002Fimages\u002Fjournal\u002Fcybersecurity-trends-philippine-smes-2026-cover.webp?v=20260730u","Small business team reviewing security access controls and backup status on laptop","\u002Fimages\u002Fjournal\u002Fcybersecurity-trends-philippine-smes-2026-hero.webp?v=20260730u","Cybersecurity Trends Philippine SMEs 2026 | PrimeCode","Cybersecurity trends for Philippine SMEs in 2026 — phishing, backups, vendor access, and Data Privacy Act basics that matter before you buy more tools.","\u002Fimages\u002Fjournal\u002Fcybersecurity-trends-philippine-smes-2026-og.webp?v=20260730u","2026-08-31T01:00:00.000Z",31,"\u002Fblog\u002Fcybersecurity-trends-philippine-smes-2026",{"slug":46,"title":47,"description":48,"category":8,"readTime":9,"tags":49,"coverImage":52,"coverImageAlt":53,"heroImage":54,"heroImageAlt":53,"metaTitle":55,"metaDescription":56,"ogImage":57,"noindex":20,"published":21,"publishAt":58,"sortOrder":59,"updatedAt":58,"status":24,"path":60},"laravel-cms-vs-wordpress-philippines","Laravel CMS vs WordPress in the Philippines: they are not the same product","Search lumps Laravel CMS and WordPress together. One is a publishing tool; the other is software with an editorial screen. Here is how Philippine teams should choose.",[11,50,51],"WordPress","CMS","\u002Fimages\u002Fjournal\u002Flaravel-cms-vs-wordpress-philippines-cover.webp?v=20260730u","Editor comparing a content management dashboard with a custom application admin","\u002Fimages\u002Fjournal\u002Flaravel-cms-vs-wordpress-philippines-hero.webp?v=20260730u","Laravel CMS vs WordPress Philippines | PrimeCode","Laravel CMS vs WordPress for Philippine businesses — when a CMS is enough, when you need a Laravel app, and when a hybrid stack fits.","\u002Fimages\u002Fjournal\u002Flaravel-cms-vs-wordpress-philippines-og.webp?v=20260730u","2026-09-04T01:00:00.000Z",34,"\u002Fblog\u002Flaravel-cms-vs-wordpress-philippines",[62,64,79],{"slug":46,"title":47,"description":48,"category":8,"readTime":9,"tags":63,"coverImage":52,"coverImageAlt":53,"heroImage":54,"heroImageAlt":53,"metaTitle":55,"metaDescription":56,"ogImage":57,"noindex":20,"published":21,"publishAt":58,"sortOrder":59,"updatedAt":58,"status":24,"path":60},[11,50,51],{"slug":65,"title":66,"description":67,"category":8,"readTime":9,"tags":68,"coverImage":70,"coverImageAlt":71,"heroImage":72,"heroImageAlt":71,"metaTitle":73,"metaDescription":74,"ogImage":75,"noindex":20,"published":21,"publishAt":76,"sortOrder":77,"updatedAt":76,"status":24,"path":78},"when-to-migrate-off-wordpress-philippines","When to Migrate Off WordPress: A Practical Guide for Philippine Businesses","WordPress got you online. Slow plugins, fragile updates, or ops workarounds may mean it is time to leave. Here is when to migrate — and when hardening is enough.",[50,69,13],"Migration","\u002Fimages\u002Fjournal\u002Fwhen-to-migrate-off-wordpress-philippines-cover.webp?v=20260730u","Business team planning a website migration from WordPress to a custom stack","\u002Fimages\u002Fjournal\u002Fwhen-to-migrate-off-wordpress-philippines-hero.webp?v=20260730u","When to Migrate Off WordPress Philippines | PrimeCode","When to migrate off WordPress for Philippine businesses — stay-and-harden signals, migration phases, and when a custom Nuxt + Laravel stack fits.","\u002Fimages\u002Fjournal\u002Fwhen-to-migrate-off-wordpress-philippines-og.webp?v=20260730u","2026-08-21T01:00:00.000Z",28,"\u002Fblog\u002Fwhen-to-migrate-off-wordpress-philippines",{"slug":80,"title":81,"description":82,"category":8,"readTime":9,"tags":83,"coverImage":85,"coverImageAlt":86,"heroImage":87,"heroImageAlt":86,"metaTitle":88,"metaDescription":89,"ogImage":90,"noindex":20,"published":21,"publishAt":91,"sortOrder":92,"updatedAt":91,"status":24,"path":93},"laravel-vs-wordpress-for-business-websites","Laravel vs WordPress for Business Websites: A Practical Comparison","WordPress is everywhere. Laravel powers serious applications. Here is when each fits Philippine business websites — and when a hybrid or custom stack is the better call.",[11,50,84],"Websites","\u002Fimages\u002Fjournal\u002Flaravel-vs-wordpress-for-business-websites-cover.webp?v=20260730u","Developers comparing web platform architecture options at team desk","\u002Fimages\u002Fjournal\u002Flaravel-vs-wordpress-for-business-websites-hero.webp?v=20260730u","Laravel vs WordPress for Business Sites | PrimeCode","Laravel vs WordPress for Philippine business websites — fit, limits, and when to choose custom development.","\u002Fimages\u002Fjournal\u002Flaravel-vs-wordpress-for-business-websites-og.webp?v=20260730u","2026-08-19T01:00:00.000Z",27,"\u002Fblog\u002Flaravel-vs-wordpress-for-business-websites"]