No foreign key definition for parentClass?

I'm working with a pretty extensive Revo 2.1.3-pl site, using a lot of custom manager pages with my own custom database tables and schemas... I'm getting a lot of errors like this in the logs:



I referenced some MODx database keys (e.g. the user id) in some of my tables, but I didn't touch the core modx.mysql.schema.xml flie to make the relations 2-way. Could that be what causes this error?

I guess you could temporarily edit the core schema and related class files to add in the relationship. I wonder if you can redefine modUser and it's relations within your custom schema - haven't tried it but sooner or later will need to do something like that!

Yeah... I know I can edit the core schema and regenerate its classes, but I've been reluctant to do that. MODx is kinda scary with how easily it creates database tables -- it's scary because it just as easily can blow away database tables, so I had to be really careful about redefining schemas when I had data in my database.

I found the cause of my particular problem I think... I was binding a query on modUser, but I had deleted that column from my table. I commented out a block of code, and the error disappeared. Good enough for me for now.

FWIW, you can extend modUser and add relations to your custom tables. Similar approaches can be used with other classes in the framework, but we'll need to talk specifics beyond extending modUser.

So when you extend modUser (or any built-in MODx class) by adding extra data to a separate table that uses the MODx key, should you edit the MODx schema file and regenerate classes to make the relationship 2-way? I wouldn't think that any of the built-in MODx stuff would use any of the custom data, so in my mind, I didn't think there was a good reason to modify the MODx schema.

The other reason was simple: I wanted my info to persist in my tables even if a MODx user was deleted. Maybe that's not the right way to approach it, but it worked.

Could you have just marked the user as inactive?

You don't need to modify the MODX schema. Just extend modUser and add the relations into your extended class...

Cool, that's what I did.

I'm having the same problem. I've posted info here: https://forums.modx.com/thread/72215/xpdo-schema-relationships-help. Did you ever figure this out?

Yeah: it was caused by an incorrect relationship. I corrected the schema/database and then updated my getCollection and getCollectionGraph methods that incorrectly tried to join on a relationship that did not exist.