-
- 2,877 Posts
-
- 964 Posts
yep, that is the problem... client has to remember the name of the image instead of selecting by seeing the image!
Website: www.mercologia.com
MODX Revo Tutorials: www.modxperience.com
MODX Professional Partner
-
- 2,877 Posts
Too bad that didnt do it...
Maybe someone else have suggestions?
-
- 70 Posts
warenhaus, charliez, check out carefully:
Tools > Configuration > File Manager, check under File Manager Path
it should be something starting with
home/.... and ending with the name of the .../directory your MODx is residing in
and take a copy of that address
move to Tools > Configuration > Interface & Features
find Resource path (10 or 11 down) and paste the address and add behind it: assets/
go one down find Resource URL and just only put assets/ in it.
this works for us in all 0.9.6.3 sites now.
the two reported problems are gone.
l
-
- 84 Posts
unfortunately, this doesn’t help.
as mentioned in my initial post, I actually copypasted the filemanager-adress as you described. it looks like this: /srv/www/vhosts/MYDOMAIN/htdocs/
I tried to remove the starting /, but then the neither the filemanager nor the resource-browser work correctly.
no luck here.
-
- 964 Posts
nope, if I do what you say I get a blank resource manager
the files dont even appear in the window...
Website: www.mercologia.com
MODX Revo Tutorials: www.modxperience.com
MODX Professional Partner
-
- 2,877 Posts
Maybe re-transfer files and upgrade (
w/o installing demo page) modx...
-
- 70 Posts
check Tools > System Info
and View phpInfo()
scroll down to Environment
under WN_ROOT find the beginning of the correct address, usually running from /home/.. to the /www level,
usually the entrance adress of your site.
copy that address and add your directories to the one housing MODx
then you have the address as mentioned in the instructions above correct
and just need to add the assets-directory as indicated and off you go.
as this address includes your personal data do never publish it in fora etc !
lmv
-
- 84 Posts
I have no WN_ROOT, I see a DOCUMENT_ROOT, however, which is the same address that I cited above.
as the MCPUK-browser seems to actually know the right path (once I click the image, it is correctly selected and displayed for FCKeditor, same thing if I click to edit the image: all works fine), the issue must be related to the (displaying of) thumbnails. They do exist in the folders, I checked it.
Is there an easy way to modify the mcpuk-connectors so that to simply show the actual image, instead of a thumbnail it seems not to be able to find?