Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

relative position of dragged file doesn't work... #22

Open
partikule opened this issue May 3, 2011 · 4 comments
Open

relative position of dragged file doesn't work... #22

partikule opened this issue May 3, 2011 · 4 comments

Comments

@partikule
Copy link

Even the padding size is OK, the relative pos doesn't work.
The container should have a good position... no ?

@GerHobbelt
Copy link
Owner

On Tue, May 3, 2011 at 5:21 PM, partikule <
reply@reply.github.com>wrote:

Even the padding size is OK, the relative pos doesn't work.
The container should have a good position... no ?

Damn.

Well, in standalone mode, the container div is a thin line somewhere in the
page and certainly not indicative of the position of the filemanager as you
see it on screen.

Do you have a test URL where I can see this going wrong?

Met vriendelijke groeten / Best regards,

Ger Hobbelt


web: http://www.hobbelt.com/
http://www.hebbut.net/
mail: ger@hobbelt.com

mobile: +31-6-11 120 978

@GerHobbelt
Copy link
Owner

See the latest commit; a few changes related to drag & drop; the d&d should now work for all modes, no more hackiness in that section. Also note the related move/copy/can't-drop-here iconography.

@partikule
Copy link
Author

Great !

Will have a look tomorrow. Have worked alot for my clients these days and I think I will be full tomorrow, but...

See you soon Ger !

My next mission : fighting with Mimes and find a solution to allow only some kings of files in ionize.. (PDF for example....)

Le 25 mai 2011 à 00:40, GerHobbelt a écrit :

See the latest commit; a few changes related to drag & drop; the d&d should now work for all modes, no more hackiness in that section. Also note the related move/copy/can't-drop-here iconography.

Reply to this email directly or view it on GitHub:
#22 (comment)

@GerHobbelt
Copy link
Owner

On Wed, May 25, 2011 at 12:49 AM, partikule <
reply@reply.github.com>wrote:

Great !

Will have a look tomorrow. Have worked alot for my clients these days and I
think I will be full tomorrow, but...

See you soon Ger !

My next mission : fighting with Mimes and find a solution to allow only
some kings of files in ionize.. (PDF for example....)

You mean on upload through filemanager?

In that case, do the additional permission checking in the FileManager
callback (hook) for the upload event. You can either throw an Exception for
each 'illegal' file being uploaded or simply return FALSE when you don't
accept the upload (this will send an authentication error report to the
client).
See Demos/FM-common.php for a very basic example how to do a
UploadIsAuthorized_cb hook function.

Inside the hook handler, you have full access to the getID3-determined mime
data, etc. as it all sits inside the fileinfo struct parameter. Heck, you
can even tweak that data, if you really want that (but that would be
highly advanced usage of the MTFM and not a 'regular thing to do')!

The Demos/FM-common.php file has the hook example here:

function FM_IsAuthorized($mgr, $action, &$info)
{
...
}

and the contents of $info et al are documented at the top of
FileManager.php, starting at the line
Hooks: Detailed Interface Specification

and then specifically section
'upload'

Met vriendelijke groeten / Best regards,

Ger Hobbelt


web: http://www.hobbelt.com/
http://www.hebbut.net/
mail: ger@hobbelt.com

mobile: +31-6-11 120 978

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants