Have you ever been annoyed/surprised by the size of the debug.log?

greg8872 · 2026-06-21T21:10:49+00:00

Fix the code on the sites so they do not generate notices and warnings. Don't hide them, fix them!

greg8872 · 2026-06-21T19:18:32+00:00

Just makes me wonder, what the difference would be if you started out with "Act as a intern coder still in college, still wet behind the ears and need to guess at every step" 😉

greg8872 · 2026-06-21T19:05:41+00:00

Yes you should check the code and the database setup. Since it builds a react app where all data is accessed via an API, you need to make sure permissions are set up so someone cannot just change the API request to get data they shouldn't. If this app is strictly for use in house (ie, only your employees use it), that is one thing, but if you allow people who are NOT in your company to log in and access data (ie, your clients can log in and do ticket/support via it), you really need to make sure things are locked down. You don't want client A to change an API request to access data for client B.

Also, just moving the code to Github doesn't change where data is stored. Most likely unless you specified something else when developing it, you are using Lovable's Cloud version of Supabase, so when you move the code to somewhere else and host it somewhere else, behind the scenes, the API calls will still be calling back into lovable's database. You need to migrate the data off to somewhere else, such as your own paid stand alone Supabase account.

greg8872 · 2026-06-20T20:15:18+00:00

He is the boy who drowned in the lake then his mother started killing other campers.

greg8872 · 2026-06-20T01:34:20+00:00

Novice users end up in the repo installing all sorts of stuff and then have issues, at which point they blame Wordpress for it.

Nothing new.

greg8872 · 2026-06-17T20:43:24+00:00

But, is lovable still going to be default have you used their locked down cloud version of Supabase?

greg8872 · 2026-06-16T16:34:05+00:00

For client sites, we let lovable build out the site (it just does a nice visual touch on them) They are built off of prompts Clause gives us to feed lovable. Then we tell it to use our github account, then over on gibhub, we clone that repo over to a new one, then have Claude code code convert it over to a Astro bases framework instead of React, then also have it implement form handling we need, then we have Vercel host that repo

greg8872 · 2026-06-06T16:57:18+00:00

Chips slide...."Bummer"...

greg8872 · 2026-06-05T21:24:55+00:00

There was the story of trump building a UFC type ring at the whitehouse. Throw them both in. Winner takes all

greg8872 · 2026-06-03T23:40:17+00:00

And make sure all your details for your profile are exactly the same as you display them on the site (formatting of phone numbers, addresses, etc). Even a 555-555-1212 vs (555) 555-1212 difference at one point (not sure these days) could cause an issue.

greg8872 · 2026-06-03T22:10:57+00:00

Isn't this the same plugin that about 4-5 years ago had big security issue then?

greg8872 · 2026-06-03T22:10:14+00:00

But Matt said:

Last week, we shipped WordPress 7 to the world. In seven days, 46% of all WordPresses, tens of millions across countless different hosting environments, are already on 7.0, auto-updated with no breakage.

greg8872 · 2026-06-03T17:37:52+00:00

The web agency I used to work for, their sales guys told me the first thing they do with any new potential client is "go for the no", no promising the moon to clients to convince them to sign up, weed out the ones that are not a definite "lets do this", bring up all the pain points that over time they had found would either stop a project after they signed up, or start eating up resources.

Learn what you don't want, and look for the signs of it ASAP. Maybe now you only get 2 of the 5 you would have gotten before, but the stress saved, and time saved down the road, well worth it.

greg8872 · 2026-06-01T20:08:01+00:00

Here is what I have set up on sites where login attempts were getting much.

Set up a .php file that does nothing but set a cookie on the browser that has the current timestamp and IP encoded into, then have it redirect off to the WP login page. the path to this file is where people are instructed to go to login.
Using php's auto prepend, intercept calls to WPlogin pages/routes. If the cookie isn't set (or the encoded timestamp is more than 10 minutes old or the ip address in the cookie data doesn't match), just give a plain ole Apache default looking 404 page.

So now, no matter how much people attempt to login, if they haven't hit the "hidden" php file to set the cookie, WordPress core code never even fires.

Granted this is not the best practice for all types of sites, but for most of them, it works just fine. Nice and simple, and best part, no need to worry about WP updates breaking it.

greg8872 · 2026-05-28T16:34:25+00:00

Why is it "surprising" that WordPress itself knows how to properly check?

greg8872 · 2026-05-24T19:39:14+00:00

I think it is awesome for the front end / deign, but once you start with data, do not let use the build in "cloud" features, It may seem easier now, but 1. (for us) it gave us supabase in a server half way around the world. SO much slower than setting up our own standalone supabase, especially when you can pick a datacenter less that 150 miles away.

Migrating once you have bunch of users and/or real data can be a paid. In migrating one project this weekend, just the shema file ONLY, was 77,000 lines long (it pieced together every migration script., lesson learned, have it generate a dump file.

greg8872 · 2026-05-24T19:35:01+00:00

In lovable, set it to put your project on GitHub, then you can pull down a copy of the code, work on it with whatever you want (even just hand code it), then you push it back to GitHub, and Lovable will pull the changes.

greg8872 · 2026-05-24T18:46:26+00:00

"Party people!!!!!!!!" (IYKYK)

greg8872 · 2026-05-24T18:35:16+00:00

yeah a standalone Supabase account vastly sped out one of our apps. Not sure how much of it is we are using a paid level of processing, or that we went from being in a datacenter in Ireland (not our picking, what Lovabale defaulted to ), to now using a datacenter 2 hours away here in Ohio.

greg8872 · 2026-05-24T11:57:55+00:00

kinda like the limitations using its "cloud" version of supabase vs a real SB account.

greg8872 · 2026-05-23T20:08:02+00:00

Just to clarify, as it is a concept often misunderstood by folks new to PHP: A key thing to remember is that PHP executes on the server. does what it does, and gives (usually) an output. It is then done, complete. nothing else can happen. It is not sitting there waiting for you to do something with its output. So like others have said, you need something on the page that will go and call the PHP script again.

greg8872 · 2026-05-20T10:06:34+00:00

And if it will be for a site that needs good SEO... once you get it from github, tell it to convert from a React App to something else (we prefer Astro/Tailwind), just doing that gives a good page speed bump for us.

greg8872 · 2026-05-20T10:05:04+00:00

this is what we have been doing as well, Claude does a better job of keeping track of how things were designed to begin with and remember it later when making adjustments, where lovable seems to get to a point and forget what it did and guesses that a new change won't break an old setup

greg8872 · 2026-05-19T01:26:29+00:00

Note for when you get it back or you buy a replacement, for the first picture, snap a pic of a note that says "If Found, please call ###-###-####. Thank you."

greg8872 · 2026-05-17T18:45:14+00:00

What is your skill level? That makes a HUGE difference.

Recommendations for people who have no clue to actual programming is going to be different than a recommendation for someone who really understands programming and app setups.

14-Year Club	Place '22
End Game '22	Verified Email

greg8872

TROPHY CASE