Agreement Page module has finally died

[lesliekirk]

The Advanz Design Agreement Page module has finally rode off into the sunset. It's a heavily relied-upon module for one of my clients. It inserts itself between the OCST page and the OSEL page. If the customer doesn't agree, it doesn't let the customer proceed any further. I'm assuming it had originally been put in place because there was nothing else that would enable the (automatic) insertion of a page between the OCST and OSEL pages.

I am already thinking through a few things about how to replace this. Can I change the Continue to Shipping button so it links to the Agreement page, and then the "Agree" button proceeds to the OSEL without confusing the process?

Has anyone else created a REQUIRED agreement that must be clicked/checked before proceeding? I would have turned to the EP Addendum module, but it's obsolete too.

The module just made it so simple, no jumping through coding hoops.

All ideas are welcome. I need to get the module removed because it's throwing a runtime error; the license can no longer be validated because the domain is gone.

[Kent Multer]

I wrote a module for that in 2004. It's obsolete now, of course. But in general, thanks to page templates, this is pretty easy to do. If you get stuck, you know who to call. :^)

Instead of creating a new page, it might be easier to put the agreement text and checkbox on the OCST page, just above the Continue button.

[Rick Wilson]

I suspect you could build this with Claude or Chat easily.

[lesliekirk]

Instead of creating a new page, it might be easier to put the agreement text and checkbox on the OCST page, just above the Continue button.

I had thought about the checkbox on the OCST page, but it needs to be required. Sure, it could be done within the field, but the store owner wants it to be foolproof/failproof. (I guess I need to go back and beg for required custom fields).

Another thing the store has on the Agreement Page is a conditional that checks to make sure the International country orders meet a minimum requirement (with the exception of 2 countries). If the amount hasn't been met, then they are asked to continue shopping. (Yeah, all of this would have to ve redone too)

[lesliekirk]

I suspect you could build this with Claude or Chat easily.

LOL, every time I try to use AI, the code blows up...hmmmm, it's been a few years since I've crashed a server....

[Rick Wilson]

If you have paid ChatGPT, I'd test the Codex App using ChatGPT6 Astra, it's... a new level of ability.

[Bruce - PhosphorMedia]

If you use a simple javascript or jquery check box to enable the continue button to be active you can simply foolproof it by placing a test for that field value being present on the following page. For example if the input check box on OCST name is 'Iagree' the Jquery will detect it being checked to enable the continue button, But you then wrap a meta refresh html statement On OSEL page that sends them back to OCST if that valuye is not present. Include a cgi parameter such as noagree=1 and use that to pop up a message on the returned OCST page saying they have to agree.

[lesliekirk]

If you have paid ChatGPT, I'd test the Codex App using ChatGPT6 Astra, it's... a new level of ability.

Sidebar on all of this AI stuff. I thought it was really cool, and it felt great when I used AI to redo a javascript function. Call it soul-searching (it made me think about AI-generated music), but I know there are still a few developers out there who are trying to do this stuff. For almost 30 years now, I have never tried to take that away from them. I am an integrator who searches for the best person to do the job. With that said, I really would like to get a good handle on using AI with Miva (I've gotten really good at using it for blog posts and product descriptions), just as I've tried to make tweaks to Page Builder Components (on a Mac).

As for the required custom fields, I have probably already requested this feature, but I will bring it up again.