Support for web publishing

[GoogleCodeExporter]

Hello, just a quick question.

I have enabled "expose-file-links" in index.html but is there anyway to get the 
real links for a file.

I'm trying to copy an image real URL because <img tags inside flash don't like 
the public link.

Thank you and keep up the good work!

Original issue reported on code.google.com by hugoemor...@gmail.com on 6 Feb 2012 at 7:50

[GoogleCodeExporter]

I have read the security wiki and I understand this software is designed to 
never expose direct links to the files (even if a published folder is visible 
by the web).

I am using the CKEditor plugin which is great, I am trying to integrate 
CKFinder and so far I have not had much luck.

This is what I have in 
/backend/plugin/FileViewerEditor/editors/CKEditor/resources/mollify.js

var editor = $('#ckeditor').ckeditor({

        removePlugins : 'resize',
        fullPage: true,
        filebrowserBrowseUrl : '../ckeditor/ckfinder/ckfinder.html',
            filebrowserImageBrowseUrl : '../ckfinder/ckfinder.html?type=Images',
            filebrowserUploadUrl : '../ckeditor/ckfinder/core/connector/php/connector.php?command=QuickUpload&type=Files',
            filebrowserImageUploadUrl : '../ckfinder/core/connector/php/connector.php?command=QuickUpload&type=Images',
            height: 300,
                  ....     

Paths are correct and ckfinder works standalone: 
http://manus.ws/art/backend/plugin/FileViewerEditor/editors/CKEditor/ckfinder/ck
finder.html

I'm attaching the full JS file and I was also wondering how can I use mollify 
authentication in ckfinder (if possible).

Thank you!

Original comment by hugoemor...@gmail.com on 7 Feb 2012 at 4:39

Attachments:

• mollify.js

[GoogleCodeExporter]

Sorry, not familiar with CKFinder, so can't help here. I was just wondering, 
isn't CKFinder file manager just like Mollify, what are you trying to achieve 
with using both of them simultaneoisly?

Anyway, I don't have plans in supporting CKFinder.

What comes to links, you are right about the "real links" if you refer to 
direct web server links, having them would make Mollify useless because there 
would be no control on how can access them.

Original comment by samuli.j...@gmail.com on 8 Feb 2012 at 5:38

• Changed state: WontFix

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Hello again and thank you for the reply. I believe I wasn't very clear before 
so I apologize, let me explain what my goal was when asking for your help.

CKeditor is a HTML editor and it does a great job at that, however, when 
someone tries to add an image inside CKeditor the standard way of doing this is 
by specifying a URL. 

I can of course upload images using mollify but I have no way of getting the 
direct URL to use in CKeditor.

CKfinder is (to me) very different as I would only be using it for image 
integration part of CKeditor and only because I couldn't think of another way 
to insert images.

My goal was to be able to use CKeditor as a little backoffice for a flash site. 
this is why I stated that Public Links did not work.

I really like the plugin and it works very well, the only drawback to me is the 
impossibility to add images (or other content) to the HTML file you're editing.

I hope I was clear this time as to what I was trying to achieve ;)

Original comment by hugoemor...@gmail.com on 9 Feb 2012 at 3:32

[GoogleCodeExporter]

Yes, CKEditor is familiar to me, naturally, as there is a plugin for it.

Mollify is not meant to be web page publishing system, ie you really should not 
use Mollify links in a HTML page.

What I suggest is that you publish a folder from your web root into Mollify, 
then you know what is the url to this folder and its resources. For example, if 
you have web root "/var/www/" and you publish folder "/var/www/mypage" in 
Mollify, you know it maps to "http://yoursite/mypage". When you open "mypage" 
in Mollify and upload "image.png" into it, you know it maps into 
"http://yoursite/mypage/image.png", and so on.

Original comment by samuli.j...@gmail.com on 9 Feb 2012 at 9:42

[GoogleCodeExporter]

Thanks for the reply, I already have a published folder that is inside my web 
root. 
No problem there, but this still means that the final user has to input url 
manually and not just the image name. 
I'd rather not have users write anything manually for obvious reasons. 

Now I'm looking at a way to have a default url in the input field when the 
image icon is clicked in CKEditor, something like: "http://yoursite/mypage/" 
this way the user would just have to paste the file name.

I understand of course that mollify is not a web publishing system, I'm just 
trying to get the most out of the available features and adjusting them to my 
needs, same as everybody.

thanks for your help though, and thanks also for the well organized CSS which 
allows us to customize pretty much anything.

Cheers

Original comment by hugoemor...@gmail.com on 9 Feb 2012 at 11:06

[GoogleCodeExporter]

Yes, I understand. I thought this was for your own use and not end users, which 
makes it different.

The thing is, Mollify cannot know what url does the folder map into, so this 
would have to be some kind of meta data in the backend folder settings. And I 
haven't investigated CKEditor that much, can't say how would this integrate 
nicely, but I guess I could look into this when I have time, but honestly my 
current road plan indicates it does not happen any day soon, unfortunately.

Original comment by samuli.j...@gmail.com on 9 Feb 2012 at 11:49

• Changed title: Support for web publishing
• Changed state: New

[GoogleCodeExporter]

Hello again,

Sorry to reopen this issue but... I was just browsing through the demo at the 
official site and the Public Links seems to to exactly what I need! ie 
"http://www.mollify.org/images/mollify_logo.png"  instead of the mollify 
encoded URL.

Can you tell me what version of mollify this is? Could I use it?

Thank you for your time

Original comment by hugoemor...@gmail.com on 16 Feb 2012 at 11:25

[GoogleCodeExporter]

Demo site does not use any backend, so it fakes many things just to demonstrate 
how it would look like in real installation. But the demo concept has been 
obsolete in many ways, and I'll remove it soon.

So real installation won't have anything like that, because a) Mollify is not 
meant for this as it is b) nor could Mollify even give you the url because it 
needs the metadata.

Original comment by samuli.j...@gmail.com on 17 Feb 2012 at 5:36