chrizz Reply #1, 4 months, 1 week ago
Hi everyone,
I'm thinking about to extend the regular site_content table, because I need a lot more information for some resources (it will become a gallery).
First try: I used TVs. Unfortunately a lot of TVs slow down the page speed.
Now I have two ideas but I don't know which one will be the MODx way
1)
Using one TV, storing all data as JSON
=> fast but for sorting I need to sort an array. Can't be done by MySQL
2)
Extending site_content table with a custom table (as described here mit modUser http://rtfm.modx.com/display/revolution20/Extending+modUser )
=> defining a new class_key for all the gallery resources (single pictures), sorting via tables
I'm new on this level of developing and I hope someone will give me a hint. Perhaps I didn't realized that there's a third possibility or a improvement for 1 or 2
thanks a lot!
I'm thinking about to extend the regular site_content table, because I need a lot more information for some resources (it will become a gallery).
First try: I used TVs. Unfortunately a lot of TVs slow down the page speed.
Now I have two ideas but I don't know which one will be the MODx way
1)
Using one TV, storing all data as JSON
=> fast but for sorting I need to sort an array. Can't be done by MySQL
2)
Extending site_content table with a custom table (as described here mit modUser http://rtfm.modx.com/display/revolution20/Extending+modUser )
=> defining a new class_key for all the gallery resources (single pictures), sorting via tables
I'm new on this level of developing and I hope someone will give me a hint. Perhaps I didn't realized that there's a third possibility or a improvement for 1 or 2
thanks a lot!