Commit Graph
13 Commits
Author SHA1 Message Date
Parsa Aghayi d4f41b9c2e Store contact messages in DB and seed real bilingual blog content
Deploy Backend / deploy (push) Successful in 2m40s
Contact form messages were sent via mailto and the site has no mail
service, so visitors saw a placeholder caveat instead of a working
channel. Add a contact_messages table, a public throttled POST endpoint,
and admin list/mark/delete endpoints, then wire them into the panel.

Replace the faker-generated blog demonstration content with real
English and Persian SEO-oriented articles via RealBlogContentSeeder
(deterministic, bilingual posts with per-language categories and tags,
and cross-linked related posts).
2026-10-02 05:41:05 -04:00
Parsa Aghayi 99f786265e Let the admin panel manage services, skills and testimonials
These three had read endpoints or nothing at all, so their content could only
be changed by hand in the database. All writes are admin-only and rate
limited like the existing admin routes.

Testimonials are the awkward one: the migration that collapsed the legacy
per-locale tables into JSON columns deliberately skipped them, so they still
live in a child table. Testimonial therefore exposes a translations accessor
to present the same translations[key][locale] shape as Service and Skill,
which is what the generic resource form binds to. Reading the child relation
has to go through getRelation(), since a plain $this->translations inside an
accessor of that name re-enters the accessor and silently yields nulls.

The store requests now mark the NOT NULL columns as required. Leaving them
nullable let a bad payload reach the database and come back as a 500 instead
of a 422, and about_me_id is additionally a cascading foreign key.

Also registers the three resources with the admin read endpoint so the panel
can list them, eager loading the relations their forms need.
2026-10-01 18:19:32 -04:00
root 8b834189a4 Close anonymous write access to the public API and repair the broken test suite
Every mutating endpoint was reachable without authentication, so any visitor
could create, edit or delete posts, categories, tags, projects and about-me
records on the live site.

Security
- Split routes into an anonymous read-only group and a write group gated by
  `auth:sanctum` + a new `admin` middleware.
- Add `is_admin` to users; Sanctum token support on the User model.
- Add AuthController (login / me / logout). The Sanctum token is delivered in
  an httpOnly cookie and never returned in the JSON body, because the admin
  panel reaches the API through a Next.js server-side proxy that breaks
  Sanctum's first-party domain detection.
- AuthenticateAdminPanelSession promotes that cookie to a bearer header so
  Sanctum's normal validation, expiry and revocation still apply.
- Remove the unauthenticated `/user/{id}` route, which exposed user emails.
- Non-admin accounts are refused at login and the failure shape is identical
  to a bad password, so the endpoint cannot enumerate accounts.
- Fix `Route [login] not defined`: a non-JSON unauthenticated request resolved
  a route that does not exist in this API-only app and returned 500.
- Reject invalid list query parameters with 422 instead of 500, and cap
  per_page at 50 (`?per_page=100000` previously dumped whole tables).

Correctness
- Make the translation migration portable. It used MySQL-only JSON_OBJECTAGG,
  which aborted all 29 tests during migration; the data collapse now runs in
  PHP so it works on MySQL, MariaDB and SQLite.
- Add HasJsonTranslations trait providing the missing setTranslation(), which
  made project create/update return 500, and replace five copy-pasted
  getTranslation()/hasTranslation() bodies.
- Make posts.excerpt nullable to match StorePostRequest; omitting an excerpt
  was a guaranteed SQL integrity error.
- Route the AboutMeController CRUD methods that existed but were never
  registered.
- CategoryTest omitted a required description; fixed the test, the existing
  schema and validation already agreed.

Tests: 83 passing / 126 assertions (was 29 failing / 0 assertions)
2026-10-01 14:35:34 -04:00
DevOps 1a75055dd9 fix: add missing hasTranslation method to AboutMe model 2026-06-28 17:41:38 +00:00
DevOps 223a4f5640 fix: remove HasTranslations trait, use translations JSON in models + seeders 2026-06-28 17:37:08 +00:00
DevOps 4c5f6cfe10 fix: update Service model for translations JSON column 2026-06-28 15:59:20 +00:00
parsa aghaei db7ce880a0 2.1-2.4: install spatie/laravel-translatable, migrate to JSON, update models & controllers 2026-06-23 18:31:51 +03:30
parsa aghaei 1dc72d8563 1.3: fix N+1 in getTranslation by using eager-loaded collection 2026-06-23 18:10:22 +03:30
parsa aghaei cbcccfcbf8 1.1: remove dead code - old models and controllers 2026-06-23 18:07:38 +03:30
parsa aghaei 6c834607bd multilanguage updated 2024-11-03 16:01:47 +03:30
parsa aghaei 027d1090df internationalization added and backend updated until services 2024-10-23 19:06:12 +03:30
parsa aghaei d98bc7bbb0 blog api created 2024-10-13 20:16:08 +03:30
parsa aghaei bd92c3e3fc initial 2024-09-25 13:05:18 +03:30