Catalog of items

I am looking for a some kind template or modification to display items in catalog format.

Example: http://www.exapro.com/used-agie-charmilles-agietron-innovation-2-die-sinking-machine-erowa-robot-p10922216/?counter=1&category=151&page=1&exaspot=2#/?

Usually we'd just use resources for each item, with TVs for any special fields. Then display lists of items using getResources.

If you really want to get complicated, you could create a custom manager page (CMP) with custom tables. It would be easier to do this using MIGXdb for the controller. http://rtfm.modx.com/extras/revo/migxdb/migxdb.tutorials/migxdb.create-doodles-manager-with-help-of-migxdb

Thanks, MIGXdb is that i just needed.

Few more questions.

I cannot follow the example found from "MIGXdb.Create a basic gallery-management from scratch with MIGXdb" because there is no 'Configurations' title on TV settings. So what to do?

Create a new Template for our gallery-pages.
Now we create our MIGXdb - TV.
Create a new TV.
Name: mygallery
Go to the tab: 'Input Options'.
Under 'Configurations' add: 'mygallery'.
This tells MIGX to search for configurations with the name 'mygallery' This can be configuration-records as we have done above or php-files as it is done for the MIGX-configs-CMP. The MIGX-config-CMP is nothing else as a MIGXdb-CMP itself.
Add this TV to our gallery-template.
click 'Save' to save the new created TV.

Once you select a "migxdb" type TV, the Configurations field will appear. I thought I had fixed that in the docs!

Is there any ready solution available instead to doing it from scratch?

There are a few e-commerce type add-ons that handle catalogs in different ways. I'm not aware of any simple catalog add-ons.

But if you just want a simple catalog, it's very easy to either use resources with Collections to organize them and taxonomies and various tagging TV add-ons, or a MIGXdb solution.

You could also use ClassExtender to create a custom resource type that has taxonomy and tagging and other fields as part of the resource. It's better for searching and sorting that way. http://bobsguides.com/blog.html/2014/06/02/why-extend-modresource/

Quote from: sottwell at Jan 12, 2016, 11:07 AM

But if you just want a simple catalog, it's very easy to either use resources with Collections to organize them and taxonomies and various tagging TV add-ons, or a MIGXdb solution.

Ok, i choosed MiGXdb but i still can't get it working. Now i am trying to follow the "Create a basic gallery-management.." guide but cannot get anything to visible.

I created template, container and resource under it and add [[migxLoopCollection]] snippet to template but can't see anything. Datagrid is working and i can save items there.

Do you know what's wrong?

Other question: Is it possible to add a menu item for this gallery like in doodles example?

when your grid is working and you could add records, you should get the records with migxLoopCollection.

What is your migxLoopCollection-call currently?

And of course, you can have CMP like done with the doodles example for your gallery.
Just fill out the CMP-Settings and create a menu-item.

Do you want your records connected to resources with a resource_id or are they not related to resources at all?

Quote from: Bruno17 at Apr 05, 2016, 06:53 AM

when your grid is working and you could add records, you should get the records with migxLoopCollection.
What is your migxLoopCollection-call currently?
And of course, you can have CMP like done with the doodles example for your gallery.
Just fill out the CMP-Settings and create a menu-item.
Do you want your records connected to resources with a resource_id or are they not related to resources at all?

Problem solved. There was typo in the json-configuration and in a template. Menu is working fine also. Records don't need to connect resources or does it help to display the items each by each or how i can modify the output?

They don't need to be connected to resources.
This is just one way of many to create groups of records, where each group is related to one resource (by the field resource_id in this case).