youtube test

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

    Actually heres its whole answer from gpt ,to just sending back corrections instead of my simple reply:Yes. That’s the better way to handle it.
Once you have the ZIP, I’d treat it as diagnosis first, patches second:
I’d inspect the whole site so I can see how the includes, CSS, JavaScript and ASP files interact. Then for each bug, I’d give back only the smallest proposed adjustment needed, with the original section and the modified section side by side.
Something like:
Issue: mobile post column width

File:
includes/functions_format_post.asp

Original:
[relevant existing code]

Suggested adjustment:
[minimal changed code]

Reason:
[what the change is intended to fix]

Possible side effects:
[desktop layout / quick reply / quote handling / etc.]
That way he can read it, compare it against his own logic, and decide whether to use it. No wholesale rewrite and no pretending generated code should just be dropped into production.
For this old interconnected stuff, I’d also avoid changing several things at once. One change → test mobile and desktop → then move to the next bug. Otherwise you end up exactly where he is now, fixing one area and not knowing which change broke another.
So yes: ZIP in, analyse the whole structure, then return small targeted corrections for him to review.

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
kruzaroad Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: Yesterday Location: Hastings Status: Online Points: 34	Post Options Post Reply Quote kruzaroad Report Post Quote Reply Posted: 14 minutes ago at 8:47pm
	Actually heres its whole answer from gpt ,to just sending back corrections instead of my simple reply: Yes. That’s the better way to handle it. Once you have the ZIP, I’d treat it as diagnosis first, patches second: I’d inspect the whole site so I can see how the includes, CSS, JavaScript and ASP files interact. Then for each bug, I’d give back only the smallest proposed adjustment needed, with the original section and the modified section side by side. Something like: Issue: mobile post column width File: includes/functions_format_post.asp Original: [relevant existing code] Suggested adjustment: [minimal changed code] Reason: [what the change is intended to fix] Possible side effects: [desktop layout / quick reply / quote handling / etc.] That way he can read it, compare it against his own logic, and decide whether to use it. No wholesale rewrite and no pretending generated code should just be dropped into production. For this old interconnected stuff, I’d also avoid changing several things at once. One change → test mobile and desktop → then move to the next bug. Otherwise you end up exactly where he is now, fixing one area and not knowing which change broke another. So yes: ZIP in, analyse the whole structure, then return small targeted corrections for him to review.
	👍 Like (0)

Nunga Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 22 Jul 2026 Status: Online Points: 39	Post Options Post Reply Quote Nunga Report Post Quote Reply Posted: 6 minutes ago at 8:55pm
	Ive sent the file, you might want to let gpt know that i have already gone through all that with him earlier this week. so i know exactly what he will say in regards to the column problems lol and tell him no after 2 days of his 20 different code it didnt fix it lol :) The answer is in the header.asp with the fixed image size lol I will get the popcorn out and open a beer and wait :)
	👍 Like (0)

kruzaroad Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: Yesterday Location: Hastings Status: Online Points: 34	Post Options Post Reply Quote kruzaroad Report Post Quote Reply Posted: 3 minutes ago at 8:58pm
	Still waiting for it to arrive. But ill screenshot your reply and upload it to gpt.
	👍 Like (0)