CMS Made Simple Forums

I know the answer to this is probably going to be 'build your own module' but I thought I'd check and see what other module developers are thinking about doing to replace GBFilepicker in 2.0

We often use GBFilepicker to let users browse / upload files from with a module and it works well.

Has anyone managed to get GBFilepicker running under 2.0? Or have a handy suggestion for what else we could do? It seems to me that the functionality we need (file browsing and file upload) is already in the core so it seems a shame to have to replicate it separately.

Right, well given that the answer to that question was indeed a deafening silence, I went ahead and wrote a rough and ready replacement to GBFilepicker myself.

It's a very basic module that's essentially a simple wrapper around Responsive Filemanager which seemed to be the nicest open source file manager I found (it's actually released under a CC non-commercial license rather than GPL or similar so be aware what you use it for).

At the moment the module isn't really ready for public use (I needed something in a hurry) but if the interest is there then I'm happy to tidy it up and submit it to the forge.

I was wondering what would replace GBFilePicker too (and AdvancedContent for that matter). Have you tried the {content_image} tag?

I haven't had chance myself yet.

Yes, i would need GBfilepicker too for my development on cmsms v2.
Any suggestions ?
Scooper, did you manage to use Responsive filemanager
Thanks

I would be very very interested in a workable module similar to GBfilepicker. It was a great solution to what was, in all honesty, a little bit of a messy situation!

Scooper, please register some more interest in your module.

You asked for it...

The code for the module so is available now on GitHub over at

https://github.com/millipedia/MillcoBrowser

I'll submit it to the forge as soon as that's set up.

I do want to stress again that it was something I put together quickly for a project and hasn't had any kind of proper testing and is by no means beautiful.

I will try and tidy it up when I get more time (it might happen one day) but if you need something for 2.0 then give it go.

Thanks for sharing, Scooper!

Hi, stupid question time, but how do I install the module?

I assumed I would upload the zip file to the server, inside / modules directory, extracted it, set permissions @ 755, and it would be visible in the module manager, but at this stage I can't see anything.

System info copied, just in case:
----------------------------------------------
Cms Version: 2.0.1.1
Installed Modules:
AdminSearch: 1.0
CMSContentManager: 1.0.1
DesignManager: 1.0.1
FileManager: 1.5.1
MicroTiny: 2.0
ModuleManager: 2.0
Navigator: 1.0.1
News: 2.50.1
Search: 1.50.1
CGExtensions: 1.49.9
CGSimpleSmarty: 2.0.2
JQueryTools: 1.3.7
CGBlog: 1.13.1
Products: 2.24.2
FrontEndUsers: 1.30.5
FormBuilder: 0.8.1.2
CMSMailer: 5.2.4

Config Information:
php_memory_limit:
max_upload_size: 128000000
url_rewriting: mod_rewrite
page_extension:
query_var: page
auto_alias_content: true
locale:
set_names: true
timezone: America/New_York
permissive_smarty: false

Php Information:
phpversion: 5.5.30
md5_function: On (True)
json_function: On (True)
gd_version: 2
tempnam_function: On (True)
magic_quotes_runtime: Off (False)
E_STRICT: 2048
E_DEPRECATED: 8192
test_file_timedifference:
test_db_timedifference:
memory_limit: 256M
max_execution_time: 300
output_buffering: 4096
file_uploads: On (True)
post_max_size: 128M
upload_max_filesize: 128M
session_save_path: /tmp (0700)
session_use_cookies: On (True)
xml_function: On (True)
xmlreader_class: On (True)

Performance Information:
allow_browser_cache: Off (False)
browser_cache_expiry: 60
php_opcache: On (True)
smarty_cache: Off (False)
smarty_compilecheck: Off (False)
smarty_cache_udt: Off (False)
auto_clear_cache_age: On (True)
Server Information:
Server Api: litespeed
Server Db Type: MySQL (mysqli)
Server Db Version: 5.5.34
Server Db Grants: Found a "GRANT ALL" statement that appears to be suitable
Server Time Diff: No file system time difference found


Any help appreciated.

PS - thanks so much for developing the module - my clients love GBFilepicker, so not having it was a hindrance in moving to 2

Cheers,
Paul

Make sure the module directory name is MillcoBrowser rather than MillcoBrowser-master or anything else (it's probably case sensitive as well) and then it should indeed appear in your list of modules.

Hope it's useful - let me know how you get on.

Thanks so much scooper, and apologies for not replying sooner.

No problems installing once I had it named correctly, and the module is fine - perhaps not as polished as GBFilepicker, but perfectly serviceable.

Many many thanks - really do appreciate the reply, and work to adapt the module.

Cheers,

Paul

Thanks a lot for this! Hope you get time to work on this some more. If you set up a donation button, I will surely pledge a couple of bucks for your effort.

To all people who potentially would use this module:

As Scooper originally stated the package that he wrapped into a CMSMS module is licensed under the "Creative Commons Attribution Non-Commercial" license. Which means that the file picker module cannot be used for any commercial purposes what-so-ever.

It is our understanding (and we have done some research on this) that this includes but is not limited to:
- Websites for businesses
- Websites that sell products or services or accept donations (yes, even charity websites).
- Websites that include advertising (technically even google adsense).

This is just a friendly reminder that you as a developer, and ultimately your customer are responsible for ensuring that you are not violating the license conditions of any of the software that you are using.

The license for the various modules should at least be available in the help of the module, which you can read from the ModuleManager before downloading and installing the module. If not, there 'should' be a license file in the module source somewhere.

Please note: We feel the license file included with the module linked to above is incorrect, and we have messaged Scooper politely asking him to correct it.