Does anyone know if nGen FF can work with MSM weblogs or fields that have the same name? I have an installation where an nGen FF image will not show up in another MSM site.
The situation is that I am currently developing two sites for a publishing company: the smaller one is a special imprint of the larger one, so it puts out only a few books, all of which also appear in the website for the parent company.
The weblog structure for both sites is basically the same, because I would prefer to keep the weblog and field names the same in both sites, for ease of maintenance. That works successfully for every single field I have so far used ... except for the nGen FF ones.
Just to give you a bit of background, what I have is essentially something like this:
{exp:weblog:entries site=“parent|child” weblog=“catalog” status=“open|published|forthcoming”}
{cover} <—the nGen File field
{title}
{description}
... etc ...
{/exp:entries}
If {cover} is a stock-standard EE text file with a stock-standard EE image reference, there’s no problem—except for the fact that the end users seem to find the stock-standard EE procedure for uploading images too confusing, and have trouble getting the image in the right place. That’s exactly where nGen FF really shines, but obviously it’s a real problem if I can’t display the images!
I have to admit that I don’t have a lot of experience with EE yet, so it could be that I am simply going about things in a less than ideal way. Or is it just that the approach is reasonably sound, but that nGen is the one element that cannot deliver in this situation. (As I said, every other field type I have used so far seems to operate correctly across sites.)
If anyone can help me out with this issue, I’d really appreciate it!
