Hello,
Bruno recommended using bloX to manage the front end view of MIGXdb output. <-- I think that's correct.
Does anyone have a link to doc's, or even better, a link to a page that show's "bloX" being used?
Were setting up a local Toy Stores site. Eventually they are going to want to incorporate Ecommerce but are willing to allow as much testing as needed before they pull the trigger on that. Basically, they're are willing to allow their site to be used for beta testing as long as security isn't an issue.
Thanks
[ed. note: modx-rocks last edited this post 13 years, 11 months ago.]
there is no Documentation for bloX. Hoping can put together something in the near future.
one Example, where it is used to list courses on frontend (backend is done with MIGXdb)
http://www.nescot.ac.uk/further-education/apprenticeships/
all Courses are stored in a custom table.
All Categories and Subcategories are Resources.
All Course-Listings, Course-Navigations and Detail-pages are done with bloX
[ed. note: Bruno17 last edited this post 13 years, 11 months ago.]
bloX is stable, just undocumented.
It is designed to create all kind of listings.
this can be simple listing of custom-table stuff. They can also be joined to other tables, by using the joins-property.
By default it is using the default getdatas-script to create the ouput-array, but you can also create complex custom projects and tasks, where you can have your own getdatas-scripts and your own templates.
You can create nested arrays in this getdatas-script for special custom-stuff and have all chunk-files for this nested arrays also in this project/task- folder.
By default all record-chunks are files, but you can also use modx-db-chunks, if you prefer that.
If you have any questions, feel free to post them here in the MIGX-board.