TOPIC:

In __jem_cats_event_relations what is this value 'id' and where is coming from?

In short, I am trying to assign categories to venues.

Yes, it's a hair-brained idea but the lessor evil of the few available options I have to accomplish something specific that I won't go in to until I finish pulling my remaining hairs of my head.

Hi Greg,

'id' is simply a primary key without any meaning to make life easier.
Sure, catid-itemid is unique too, but Joomla likes single field keys.

Do you really want multiple categories assigned to a venue?
It's a nice and seldom feature but causes a lot of gray hairs on developers heads.
Adding a 'catid' field to venues table would be much easier to implement (but limits the usage, yes).

Thanks Hoffi. Yes, I think I have lost enough hair on this issue I have created. And I'm not even a developer.
I have walked every path on this one. Then I decided I simply need more functionality like that provided by categories. 2 more for venues and 1 more for events. Only 3. LOL. But alas, categories might be the most complicated thing on the platform. Granted I worked out a solution on the event side, the venue side has beaten me. Below is what I'm trying to implement a 'point and click' solution for... Going K.I.S.S though now (keep it simple stupid).

Venue #1 Has activities for: offroad cars
? 10th scale
? 8th scale
? 5th scale
? crawler
? oval
? fuel?
? electric
Venue #2 Has activities for: offroad cars, onroad cars, boats
? scales
? aspalt
? carpet
? fuel
? electric
Venue #3 Has activities for: offroad cars, onroad cars, boats, planes
? whatever boats and planes do...
Etc...

Venue #1 amenities: <some big list of things>
Venue #2 amenities: <some other big list of things>
Venue #3 amenities: <Yet another big list of things>
etc...

Event #1: <some specific big list of activities and amenities>
Event #2: <some other specific big list of activities and amenities>
Event #3: <Yet another specific big list of activities and amenities>
etc...

Actually, I might as well spill the beans (not glamorous or a rec'ed path). This is what I came up with in 'events':

Yes, it's OK to be amused and laugh, and even wonder, "WT$*^@#?"

1. Added a bunch of unpublished dummy categories to my existing extensive list (low ID# reservation).
2. Created a new category under root.
3. Fingered the ID# of the new cat to 1000 in the DB.
4. Created child cats under the parent ID #1000 (auto increment 1001, 1002, etc).
5. Changed the event edit view to:
A: Show < ID #1000 in normal cat presentation.
B. Show > ID #1000 in new line.
Ouput-
Categories: <normal blah, blah, blah>
Amenities: <new stuff blah, blah, blah>

This is where I moved to 'venue' and realized all the code I was going to have to change if I were to stay in just 'views' with the crazy mod. It was an impressive mess though and worked. LOL

And so it is that I can't beat this dead horse enough. I have come full circle around 4 or 5 times now.

I have decided that for my specific needs that doing nothing to this regard is going to be more costly than doing nothing- on numerous fronts.

Here is my latest idea. Feedback would be greatly appreciated and can run from, "You are an idiot". To, "You are a genious".


1. Store unique list of assignable venu attributes in new custom table. (DONE)

2. Dynamically populate and echo Joomla checkboxes form field type from custom table. (SCRIPTING DONE IAW JOOMLA STANDARDS. OUTPUT PENDING)

3. Store selections in new single imploded custom venu table. (IN PROCCESS)

4. On edit, explode custom venu table containing previous selections and ensure no overrides or dups (maintain old selections) of existing data and inclusion of any new fields. (IN PROCESS).

Do share!

Sorry, actually our time is very limited and we are working on other things. And now reactions from other users shows me, that there is no such need from other users. Socthis has absolutely no priority, apologies.