Resource Browser in 2.1.2 shows image boxes but not images. As does TinyMCE.

Since starting to use Revo I have been unable to see images with the mgr context.

I can locate the image filename in the resource tree when adding them to a TV, or inserting them into a richtext edit field like [[*content]] using TinyMCE, but I can’t see the image. When it is an image TV, there is no preview of the image in the resource page. In IE I get a little red cross, in Chrome I get the broken-image icon, in Firefox I get blank space within the thumbnail frame. No matter whether it is Tiny MCE or the MODx Browser, it looks the same.

This is an improvement: I was following another thread on a similar topic http://modxcms.com/forums/index.php/topic,63523.0.html which put the issue down to some problems with compressed and concatenated js files. I had followed the patch instructions and obtained the current status quo as a result. Hitherto I had not even been able to see empty boxes.

Well, the new release means that I can see empty boxes without doing all that patching and replacing.

I get the same effect whether I set Use Compressed to Yes or No.

So whatever is wrong with my set up, it isn’t the javascript thing.

Anyone else got this? My current set-up is below. Any ideas?

I’ve just upgraded to 2.1.2 and had the same problem - it turned out that in my config.inc.php, some of the directories had the wrong case (instead of MyName it was myname), which was messing up the paths. Have a check and see if that’s any help.

Prior to 2.1.2, the fixes that splittingred submitted had worked fine for me, and they all seem to be present in the update, so I’m going to assume your problem probably isn’t with the same files.

Sorry - been away.

Thanks for the suggestion, but no dice.

My config.inc.php file has the correct paths: I don’t use caps in my directory structures anyway. I do use caps in sub-directories of /assets/images, but I’ve tried changing them to lower-case and all remains the same.

Elsewhere SplittingRed has suggested that perhaps some of my permissions might have prevented some of the 2.1.2 upgrade files from being written. (ther was an issue with compressed javascript files not being read correctly). I’ve laboriously gone through the entire manager tree, and while I have fond some older files, they all seem to have been superceded by being placed in new locations. None seem relevant.

There is one other factor that might be relevant, and not covered by a normal test-bed: I’m running my test site within a sub-domain - everything except images works fine, as it should, but this just might be a little unusual.

I’m at a standstill: I can only assume now it is some server/host issue which no-one else has.

Does my config look OK?



Nic Boyde