In Trongate v1, you could prevent methods from being invoked via the URL by adding an underscore to the first character of the method name.



In Trongate v2, this technique has been ditched. Now, we do the same thing with the new block_url() helper function.



A full explanation is offered here:

https://trongate.io/essays/why-the-underscore-first-convention-had-to-go

The new technique for preventing URL invocation of methods is explained here:

https://trongate.io/documentation/trongate_php_framework/intercepting-requests/preventing-url-invocation

Indeed, this was a very difficult decision but I am convinced it's the right one.

So there's no backwards compatibility?

Having multiple ways of doing the same thing isn't good. It causes cognitive dissonance in human beings and hallucinations in AI engines.

So, no backwards compatibility.

However, for you, I will say the following:

1). Let me assure you, I haven't changed personality. My thoughts regarding rewrite culture remain. T2 is 99% the same as T1. Rewrite culture still sucks. Stability continues to be my priority.

2). v1 was built like a tank and designed to last for ten years. Nothing has changed in that regard. As a matter of fact, I'm looking forward to getting the v1 docs back on the site.

3). If you have existing Trongate v1 sites out there, and you're thinking about upgrading, DON'T. At least, not yet.

I think something will be coming out - hopefully within the next month or so. Whether that's software, an upgrade list or just me hanging about YouTube all day offering technical support remains to be seen. Nevertheless, I'm confident that something is coming up and I think you should just hold onto your horses for now.