Timeline for Adding a new view to built in component (com_tags)
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 14, 2022 at 16:52 | comment | added | RogerCO | Nope. My sites are low traffic, low value, non-commercial, no logins, no visitor input, and in some cases not connected to the internet. If someone wants to waste their time fiddling with them for strange purposes so be it. | |
| Jul 13, 2022 at 8:05 | comment | added | Sharky | @RogerCO will you also be auditing J3 for security vulnerabilities? | |
| Jul 11, 2022 at 20:56 | comment | added | RogerCO | The advantage of J3 running out of official development is that the time is coming (in a month or so) when it is worth cloning J3 and then making whatever core changes I want without fear of a future new version overwriting them. That's my plan anyway, I already have several useful core hacks implemented in plugins or overrides and it'll be nice to fold them all in. I'll be sticking with J3+ for all my sites for the foreseeable future as life is too short to migrate them. | |
| Jul 11, 2022 at 20:52 | comment | added | RogerCO | Thanks, I wasn't aware of the possibility of including a new model in the template override folder - for a one-off site requirement I think I prefer this to 2. | |
| Jul 11, 2022 at 20:50 | vote | accept | RogerCO | ||
| Jul 11, 2022 at 10:17 | history | answered | pe7er♦ | CC BY-SA 4.0 |