[Solved] Ghost resources?

Hi all,

I’m trying to expand my blog by creating ghost resources. Meaning, a resource with 2 parents. It’s not doable in the manager panel, so I tried making a snippet out of it. Basically what I want is a resource that is filed under blog/section/category/resource to also appear in news/section/category/resource without creating it twice. Is this possible? And if not native, perhaps snippet worthy?

The reason why I ask this, is because I will, in the near future, also feature modx code snippets on my site. That said, the basic instructions might qualify the resource to be filed under PHP, and in the meanwhile also appear under MODx.

I’ve also tried this with symlinks, but it does not copy anything, it just redirects when clicked uppon. No content, no introtext, no pagetitle (well yea, the symlink’s but that’s not what I want).

Thanks
ReSpawN

I think that’s what tagging (using TVs) is for.

Quote from: sottwell at Jul 29, 2010, 10:09 AM

I think that’s what tagging (using TVs) is for.

Without a doubt, but that doesn’t create the same resource in another overview of a category.

I thought that was the point; to not have redundant resources?

In Revolution this is the purpose of Symlink Resource types. It allows you to create a virtual resource based on another real document resource. But in the case where the goal is to have it show in multiple categories on the front end it would be much more efficient to use tagging. You can look at this: http://svn.modxcms.com/docs/display/ADDON/tagLister and http://svn.modxcms.com/docs/display/revolution20/Creating+a+Blog+in+MODx+Revolution

Thanks, I already though it wasn’t possible what I wanted to do. No worries, I came prepared! Heh.

I was already about to include tags into my system (already created the tags TV) but I was just wondering if this was at all possible.

Thanks guys.

The question, I have is this, what would happen if you updated or edited one of the documents? Which is the master? Which is the slave? How do you know which is the original. The idea of symlinks or tagging is to NEVER have one identical document in two places. It would be a nightmare to manage.

Basically you are attempting to assign 2 parents so you can make a tag/category based taxonomy. What is the advantage of managing from two places in the back end? I assume you’d just want it to appear on the front end with the directory structure.

All I am saying is that it is possible to achieve your goal but not the way initially envisioned.

And exactly for that reason I decided not to go through with it. I’m now giving the tags a try with the tagListner from Splittingred.