kongondo

Module: Jquery File Upload

44 posts in this topic

As for your question about image replacement: I think it would be easiest to either extend FieldtypeFile or modify FieldtypeImage as a new module (and/or their related Inputfields - am not sure). What exactly are you after? I ask because I know there are some cool changes coming to the 'standard image field' and those might just meet your needs.

actually i'm only very eager about client side image resizing. i know that this is on the roadmap for 2016 but that can be everything between next blog post tomorrow and december ;) maybe you have some more details?

i'm getting offtopic here so i started a new thread in pub: https://processwire.com/talk/topic/12861-feature-wishlist-for-shortly-planned-developments/?p=116757

Share this post


Link to post
Share on other sites

Update: Jquery File Upload Version 0.0.3.

Changelog

  1. Fixed an issue that caused duplicates in image gallery
  2. Some minor enhancements
Glad to also announce that I've tested and can confirm that Jquery File Upload is compatible with ProcessWire 2.8.x and ProcessWire 3.x 
3 people like this

Share this post


Link to post
Share on other sites

Update: Jquery File Upload Version 0.0.4.

Changelog

  1. Fixed a small bug introduced during the last commit. This causes some images not to be displayed in image gallery.
1 person likes this

Share this post


Link to post
Share on other sites

@kongondo love the module, it's helped me get past a hurdle. One issue I'm encountering is uploading more diverse file types - zip and various Adobe types. Is this something that the module can support? If so, any ideas what I'm doing wrong?

I've added  allowedNonImageMimeTypes under the ajaxoptions('application/pdf', 'application/postscript', 'application/octet-stream', 'application/x-compressed', 'application/x-zip-compressed') and added the extensions to the acceptfiletypes under jfuoptions. The files show up, I get upload progress, and then I get the message:

Empty file upload result
 
Nothing shows up on the server. If I upload JPGs or PDFs - either on their own or at the same time as non-working files - they work just fine.
 
I'm on PW 3.0.42.

Share this post


Link to post
Share on other sites

@kongondo thanks - I'm new to alot of this and just starting to figure it out. These forums and the modules have taught me alot!

I don't believe any of those apply - the server is running PHP 5.4+ on Linux. 

Share this post


Link to post
Share on other sites

@Chris Whissen,

Hmm. It means, then, that the reason they are not passing validation is because they are failing the PHP mime type tests. This is either because their mime types are unknown or the 'files are not what they seem' (aka faked files)':

  • Can you confirm you are passing the allowedNonImageMimeTypes to processJFUAjax()
  • If they don't contain any sensitive data, is it possible to PM a couple of those files getting rejected to help me debug this further?

Share this post


Link to post
Share on other sites
6 minutes ago, kongondo said:
  • Can you confirm you are passing the allowedNonImageMimeTypes to processJFUAjax()

Yes. I'm doing it like this:

'allowedNonImageMimeTypes' => array('application/pdf', 'application/postscript', 'application/octet-stream', 'application/x-compressed', 'application/x-zip-compressed'),
Quote
  • If they don't contain any sensitive data, is it possible to PM a couple of those files getting rejected to help me debug this further?

No problem. I'll have something to you in a moment. I personally created the Zip in Windows and the AI in Illustrator, so they shouldn't be fake. 

Share this post


Link to post
Share on other sites

@kongondo I'm an idiot and thank you for your time and help. I reread the module a little closer and realized I need the acceptfiletypes twice - once for Ajax options and once for JFUoptions. I only had it once. Added that in and everything is working fine. Apologies for wasting your time, truly appreciate the help.

Share this post


Link to post
Share on other sites

No worries. Had just come to that conclusion just before your response. Actually, I am the idiot! I notice that 'acceptFileTypes' is not documented! Users shouldn't have to read the module code to know how to use it :o! When I get the time.....(ahem..). Yes, so what was happening is that good ol' WireUpload was rejecting those file extensions at this point. Glad you got it sorted and now thanks for the reminder that I'll need to update the docs :)

1 person likes this

Share this post


Link to post
Share on other sites

So, I'm stretching my knowledge here and can't quite figure out an issue. If I'm logged in to PW and go to front-end upload page, everything works fine.

If a guest attempts to upload a file, they get an "Internal Server Error."

I'm guessing it has something to do with the security, specifically(emphasis added):

On 1/28/2016 at 9:39 PM, kongondo said:

Server-side, no Ajax requests are honoured unless specifically set via configurable options server-side.

I'm not sure what I need to be doing for that though. I've tried to figure out on my own, but am not having much luck. Can anyone point me towards how to make this work? (Assuming there's no other obvious reason for the error.)

EDIT: Just to narrow possibilities, I created a user with guest permissions. If logged in, uploads without issue. It's only an anonymous user that can't upload. Which is an essential function for this site. Am I overlooking something obvious?

Edited by Chris Whissen
clarification

Share this post


Link to post
Share on other sites

Okay, I managed to get it to work, but I'm not sure it's the best and safest way to do it. Ran Tracey Debugger and got "This request was aborted because it appears to be forged." error message. I did some research on that and disabled protectCSRF through config.php ($config->protectCSRF = false;). Now. anonymous uploads work fine.

I'm not sure if that's the right way to do it, but I'm also not sure this is the right post to be asking - that might be more a ProcessWire issue than this module.

Share this post


Link to post
Share on other sites
16 hours ago, Chris Whissen said:

If logged in, uploads without issue. It's only an anonymous user that can't upload

Guests should be able to upload. I am not sure what's happening in your case. Just to be sure, I've double checked in PW 2.7, 2.8 and 3. Guests (meaning frontend users not logged in [anonymous if you like]) can upload just fine.

16 hours ago, Chris Whissen said:

I'm not sure if that's the right way to do it, but I'm also not sure this is the right post to be asking - that might be more a ProcessWire issue than this module.

There's no issue with the module nor with ProcessWire (I believe) in this case :). There's something else going on in your install I suspect. Some setting or hook or similar?

1 person likes this

Share this post


Link to post
Share on other sites

Thanks for looking into it @kongondo. I have quite a few modules running, so there could be something in there making a mess of things. Another mystery to solve - at least that one can wait a bit. Appreciate the help and love the module!

Share this post


Link to post
Share on other sites
35 minutes ago, Chris Whissen said:

It says the file size limit is set at 2GB, but it appears to be set at 200MB. 

Check your PHP ini for these settings:

post_max_size
upload_max_filesize

Share this post


Link to post
Share on other sites

I fixed the problem for me.  Letting you know because I think you have either a missing zero or typo in the module. It reads:

'maxFileSize' => 200000000,// 2GB

Assuming that's bytes, that equals 200MB, not 2GB - also assuming I can still do math. I added a zero and pasted it into my jfuoptions array and everything works for me. 

2 people like this

Share this post


Link to post
Share on other sites
12 hours ago, Chris Whissen said:

I think you have either a missing zero or typo in the module

Nice catch Chris. You are right. I was missing one Zero. Corrected in version 5.

Update: Jquery File Upload Version 0.0.5.

Changelog

  1. Fixed a typo in the default setting of maxFileSize. Thanks @Chris Whissen

 

 

1 person likes this

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By ethfun
      I've created a Process Module, and its execute() function renders the HTML response to an AJAX request. The AJAX request is being made outside of the admin panel, and in all likelihood will be made by "guest" users.
      Within my ModuleName.info.json file, I have added these lines:
      "permission": "generate-thumbnails", "permissions": { "generate-thumbnails": "Generate Thumbnails" }, Then within the Admin panel, I gave guests access to run that module.
      Unless logged in, the response to the AJAX request is always the login form's HTML, rather than the HTML my execute() function creates.
      So two questions:
      Is it possible to give non-logged-in users the ability to run that function via the AJAX request, or Is there a better ProcessWire way to create HTML to use as an AJAX response? Thank you!
    • By Robin S
      I have had this module sitting in a 95% complete state for a while now and have finally made the push to get it out there. Thanks to @teppo for his Hanna Code Helper module which I referred to and borrowed from during development.
      http://modules.processwire.com/modules/hanna-code-dialog/
      https://github.com/Toutouwai/HannaCodeDialog
      HannaCodeDialog
      A module for ProcessWire CMS/CMF. Provides a number of enhancements for working with Hanna Code tags in CKEditor. The main enhancement is that Hanna tags in a CKEditor field may be double-clicked to edit their attributes using core ProcessWire inputfields in a modal dialog.
      Requires the Hanna Code module.
      Installation
      Install the HannaCodeDialog module using any of the normal methods.
      For any CKEditor field where you want the "Insert Hanna tag" dropdown menu to appear in the CKEditor toolbar, visit the field settings and add "HannaDropdown" to the "CKEditor Toolbar" settings field.
      Module configuration
      Visit the module configuration screen to set any of the following:
      Exclude prefix: Hanna tags named with this prefix will not appear in the CKEditor toolbar dropdown menu for Hanna tag insertion. Exclude Hanna tags: Hanna tags selected here will not appear in the CKEditor toolbar dropdown menu for Hanna tag insertion. Background colour of tag widgets: you can customise the background colour used for Hanna tags in CKEditor if you like. Dialog width: in pixels Dialog height: in pixels Features
      Insert tag from toolbar dropdown menu
      Place the cursor in the CKEditor window where you want to insert your Hanna tag, then select the tag from the "Insert Hanna tag" dropdown.

      Edit tag attributes in modal dialog
      Insert a tag using the dropdown or double-click an existing tag in the CKEditor window to edit the tag attributes in a modal dialog.

      Tags are widgets
      Hanna tags that have been inserted in a CKEditor window are "widgets" - they have a background colour for easy identification, are protected from accidental editing, and can be moved within the text by drag-and-drop.

      Options for tag attributes may be defined
      You can define options for a tag attribute so that editors must choose an option rather than type text. This is useful for when only certain strings are valid for an attribute and also has the benefit of avoiding typos.
      Add a new attribute for the Hanna tag, named the same as the existing attribute you want to add options for, followed by "__options". The options themselves are defined as a string, using a pipe character as a delimiter between options. Example for an existing attribute named "vegetables":
      vegetables__options=Spinach|Pumpkin|Celery|Tomato|Brussels Sprout|Potato You can define a default for an attribute as normal. Use a pipe delimiter if defining multiple options as the default, for example:
      vegetables=Tomato|Potato Dynamic options
      Besides defining static options as above, you can use one Hanna tag to dynamically generate options for another. For instance, you could create a Hanna tag that generates options based on images that have been uploaded to the page, or the titles of children of the page.
      Your Hanna tag that generates the options should echo a string of options delimited by pipe characters (i.e. the same format as a static options string).
      You will probably want to name the Hanna tag that generates the options so that it starts with an underscore (or whatever prefix you have configured as the "exclude" prefix in the module config), to avoid it appearing as an insertable tag in the HannaCodeDialog dropdown menu.
      Example for an existing attribute named "image":
      image__options=[[_images_on_page]] And the code for the _images_on_page tag:
      <?php $image_names = array(); $image_fields = $page->fields->find('type=FieldtypeImage')->explode('name'); foreach($image_fields as $image_field) { $image_names = array_unique( array_merge($image_names, $page->$image_field->explode('name') ) ); } echo implode('|', $image_names); Choice of inputfield for attribute
      For attributes which you have defined options for, you can choose the inputfield that is used to select from the options.
      Inputfields that support the selection of a single option are select (this is the default inputfield for attributes with options so it isn't necessary to specify it if you want it) and radios.
      Inputfields that support the selection of multiple options are selectmultiple, asmselect and checkboxes.
      You can also specify a checkbox inputfield - this is not for attributes with defined options but will limit an attribute to an integer value of 1 or 0.
      The names of the inputfield types are case-insensitive.
      Example for an existing attribute named "vegetables":
      vegetables__type=asmselect Descriptions and notes for inputfields
      You can add a description or notes to an attribute and these will be displayed in the dialog.
      Example for an existing attribute named "vegetables":
      vegetables__description=Please select vegetables for your soup. vegetables__notes=Pumpkin and celery is a delicious combination. Notes
      When creating or editing a Hanna tag you can view a basic cheatsheet outlining the HannaCodeDialog features relating to attributes below the "Attributes" config inputfield.
      Troubleshooting
      HannaCodeDialog includes and automatically loads the third-party CKEditor plugins Line Utilities and Widget. If you have added these plugins to your CKEditor field already for some purpose and experience problems with HannaCodeDialog try deactivating those plugins from the CKEditor field settings.
    • By gRegor
      Updated 2017-03-27:
      Version 1.1.3 released
      Updated 2016-04-11:
      Version 1.1.2 released

      Updated 2016-02-26:
      Officially in the module directory! http://modules.processwire.com/modules/webmention/

      Updated 2016-02-25:
      Version 1.1.0 is now released. It's been submitted to the module directory so should appear there soon. In the meantime, it's available on GitHub: https://github.com/gRegorLove/ProcessWire-Webmention. Please refer to the updated README there and let me know if you have any questions!
      ------------
      Original post:
       
      This is now out of date. I recommend reading the official README.
       
      I've been working on this one for a while. It's not 100%, but it is to the point I'm using it on my own site, so it's time for me to release it in beta. Once I finish up some of the features described below, I will submit it to the modules directory as a stable plugin.
      For now, you can install from Github. It works on PW2.5. I haven't tested on PW2.6, but it should work there.
      Feedback and questions are welcome. I'm in the IRC channel #processwire as well as #indiewebcamp if you have any questions about this module, webmention, or microformats.
      Thanks to Ryan for the Comments Fieldtype which helped me a lot in the handling of webmentions in the admin area.
      ProcessWire Webmention Module
      Webmention is a simple way to automatically notify any URL when you link to it on your site. From the receiver's perspective, it is a way to request notification when other sites link to it.
      Version 1.0.0 is a stable beta that covers webmention sending, receiving, parsing, and display. An easy admin interface for received webmentions is under development, as well as support for the Webmention Vouch extension.
      Features
      * Webmention endpoint discovery
      * Automatically send webmentions asynchronously * Automatically receive webmentions * Process webmentions to extract microformats   Requirements * php-mf2 and php-mf2-cleaner libraries; bundled with this package and may optionally be updated using Composer. * This module hooks into the LazyCron module.   Installation Github: https://github.com/gRegorLove/ProcessWire-Webmention

      Installing the core module named "Webmention" will automatically install the Fieldtype and Inputfield modules included in this package.   This module will attempt to add a template and page named "Webmention Endpoint" if the template does not exist already. The default location of this endpoint is http://example.com/webmention-endpoint   After installing the module, create a new field of type "Webmentions" and add it to the template(s) you want to be able to support webmentions. Sending Webmentions
      When creating or editing a page that has the Webmentions field, a checkbox "Send Webmentions" will appear at the bottom. Check this box and any URLs linked in the page body will be queued up for sending webmentions. Note: you should only check the "Send Webmentions" box if the page status is "published."   Receiving Webmentions This module enables receiving webmentions on any pages that have have "Webmentions" field, by adding the webmention endpoint as an HTTP Link header. If you would like to specify a custom webmention endpoint URL, you can do so in the admin area, Modules > Webmention.   Processing Webmentions (beta) Currently no webmentions are automatically processed. You will need to browse to the page in the backend, click "Edit," and scroll to the Webmentions field. There is a dropdown for "Visibility" and "Action" beside each webmention. Select "Process" to parse the webmention for microformats.   A better interface for viewing/processing all received webmentions in one place is under development.   Displaying Webmentions (beta) Within your template file, you can use `$page->Webmentions->render()` [where "Webmentions" is the name you used creating the field] to display a list of approved webmentions. As with the Comments Fieldtype, you can also generate your own output.   The display functionality is also under development.   Logs This module writes two logs: webmentions-sent and webmentions-received.   Vouch The Vouch anti-spam extension is still under development.   IndieWeb The IndieWeb movement is about owning your data. It encourages you to create and publish on your own site and optionally syndicate to third-party sites. Webmention is one of the core building blocks of this movement.   Learn more and get involved by visiting http://indiewebcamp.com.   Further Reading * http://indiewebcamp.com/webmention * http://indiewebcamp.com/comments-presentation * http://indiewebcamp.com/reply
    • By kixe
      This morning I pushed a module to github which extends the page api with moving and sorting capability.
      https://github.com/kixe/PageSortMove
      /** * CALLABLE * PageSortMove::execute($pageID, $newIndex = 0, $parentID = null); * $modules->get('PageSortMove')->execute($pageID, $newIndex = 0, $parentID = null); * * EXTENDED PAGE API * @property $page->first // under same parent * @property $page->last * * @method $page->first($parentID = null) * @method $page->last($parentID = null) * @method $page->sort($newIndex) * @method $page->move($newIndex, $parentID = null) */ Have a nice weekend.