WordPress.org

Ready to get started?Download WordPress

Forums

NextGEN Gallery
"Import Folder" does'nt work the same way after v2.0 (34 posts)

  1. ruccc
    Member
    Posted 9 months ago #

    Before I updated to the 2.x version of this awesome plugin i did the next:
    1. Upload photos, divided by folders and subfolders on my FTP (EX: "/gallery/2010/summer/paris/" or "/gallery/2012/chris/first-birthday/")
    2. Went to "Add Gallery / Images" and to "Import Folder", then went to the desired folder with photos and improted it.
    3. Photos were'nt touched anyway by Nextgen, it only taked them a showed in the galleries.

    What happens now? With version 2.x, I do the same procedure, but NextGen is copying the photos from the subfolder to the main "/gallery/" root, and takes the photos from there.

    Is this a bug? There's no way of changing it, even with "Automatically resize images after upload" option deactivated.

    So, why NextGen is copying the photos? It only happens in version 2, can you fix it?

    MANY MANY THANKS for this plugin! It is awesome and very friendly!

    http://wordpress.org/plugins/nextgen-gallery/

  2. hephoto
    Member
    Posted 9 months ago #

    I got the same issue ...
    Hope we will get a corrected version soon.

  3. ruccc
    Member
    Posted 9 months ago #

    The only way is to downgrade to the latest 1.x version. It seems that 2.x copies the files even if "Dont resize the images" is selected...

  4. hephoto
    Member
    Posted 9 months ago #

    Okay, but I hope that it will be corrected to a next revision.Ïf not, bye bye NextGen ...

  5. Vakantie Ameland
    Member
    Posted 9 months ago #

    Same here, very annoying!

  6. mkaioh2
    Member
    Posted 9 months ago #

    same, it dont work in the new version wordpress..

  7. photocrati
    Member
    Plugin Author

    Posted 9 months ago #

    Hi all - thanks for you comments on this. You are correct that this behavior is different. It actually seems more intuitive to us to ensure NG galleries are consolidated in the folder intended to hold NG galleries. Otherwise, for users who are not systematic about where they uploading images and importing from, they could end up with NG gallery folders living all over their WP instance.

    We didn't expect that there would be much negative feedback on this.

    But having just played with this I can see that one annoying feature, even for me, is that if you'd like to organize galleries within the /gallery/ folder via FTP, and then import, you'd lose your organization. I'm assuming that what most of you are trying to do?

    Having just spoke with the developers about this, we're thinking we may add an option that allows users to either have images copied into new folders or preserve them in their original locations. I assume that would resolve things for everyone here?

    Thanks (Erick).

  8. hephoto
    Member
    Posted 9 months ago #

    Hi,

    Yes, if you could add this option, I will be happy.

    Thanks for taking car on this :)

  9. ruccc
    Member
    Posted 9 months ago #

    Hi photocrati,
    Yes, that the problem we have. That option would be great!!!

    Thanks a lot for your work! That's woth a donation! ;-)

  10. photocrati
    Member
    Plugin Author

    Posted 9 months ago #

    Ok, we've added this to our list of tasks. We're trying push out a release tomorrow but this will not be in that. We've already wrapped up work on that one and we're testing.

    It should go in one of the next releases after that, and we're doing about a release a week right now. So maybe a week or two. I hesitate to commit to getting it out faster than that since we have a lot of issues on the table still we're working through and we never know what's going to come up.

    But it's on the list now and relatively high priority.

  11. ruccc
    Member
    Posted 9 months ago #

    Don't worry, we can still use the older versions, so it's not urgent.

  12. hephoto
    Member
    Posted 9 months ago #

    Better to wait 2-3 weeks more for having a bug-less release ;)

    I've reverted back to 1.9.13 ...

  13. Vakantie Ameland
    Member
    Posted 9 months ago #

    Very nice to add that feature, will solve a lot of annoyance.

  14. mcfester
    Member
    Posted 8 months ago #

    Any update on this feature? Its the main reason I wen't back to v1.9.13 since the very first v2.0

  15. photocrati
    Member
    Plugin Author

    Posted 8 months ago #

    @mcfester and all: We've introduced a fix for this. It should be in the beta we release today (2.0.33 and later) on our latest beta page (http://www.nextgen-gallery.com/nextgen-gallery-latest-beta), and it should also then be in an official full release next Monday.

    We've added a check box on the Add Gallery/Images > Import Folder interface called: "Keep images in original location". If checked, it will keep and serve the images from their original folder.

    Thanks! (Erick)

  16. duce
    Member
    Posted 8 months ago #

    That feature is now included, but it is still limited to be inside the "wp-content" folder!
    That is really of no use as I need images in a "gallery" folder in the root folder of my website. I don't want to directly go advertise to the world where my WP installation and folder locations are.
    There is also no way you can specify the path as just "gallery" or "\usr\local\www\domain.tld\gallery\" and expect to import images from the path you have specified. It always defaults to "wp-content\" to import images.
    I understand and appreciate that your idea is for people to keep things tidy, but I prefer to keep it even tidier. It is one thing to have the default setting during install to be in the "wp-content" folder, but please just revert back to how nextgen used to work where we can specify the path explicitly and have nextgen respect what we decide.
    At this point in time I see absolutely no advantage to upgrading to the new nextgen version. To me you guys have gone a couple of steps backward and trying to re-invent the wheel.

  17. photocrati
    Member
    Plugin Author

    Posted 8 months ago #

    Hi all - An option to preserve images in their original folder is now included in the latest full releases. Thanks for your patience. Let us know if you have other issues.

    @duce: Thanks for your note. Yes, import functionality is still limited to the wp-content folder. We've had quite a bit of internal discussion about this, and it was changed for security reasons. There are some serious security concerns in allowing the plugin to access and mess around in the root directory (and all other folders) of a website. The original request to change this feature came from Automattic.

    The plugin will continue to read any galleries you've previously added from the root or other folders.

  18. duce
    Member
    Posted 8 months ago #

    Sorry, but you are missing my point.
    Even though its possible to convert the 10+ websites that currently run the Nextgen gallery system, going forward from that point it will NOT honour adding images using FTP and then importing from the specified folder in root. It will mean the images has to now be loaded in the "wp-content\some dumbass folder which already shows a potential hacker that you are using wordpress because it can only be set in a wordpress sub folder" and meaning all images indexed in search engine will display the path "domain.tld\wp-content\dumbass-folder\damn-picture.jpg"

    And as a matter of security.. I do not even use FTP. If you are really concerned about security address the core issue why websites gets hacked. Simply because noobs have no idea to set file and folder permissions and FTP clients allow for such silly mistakes, let alone the amount of FTP credentials that gets stolen daily off users pc's.

    It is neither your, nor Automattic (whoever this may be) nor my job to try and secure people's website. If it is a real concern then create documentation advising on how to secure websites and the dangers of folder permissions and locations. And at least start the documentation with: Stop using FTP at all cost, it is lazy, stupid and causes security concerns.

  19. photocrati
    Member
    Plugin Author

    Posted 8 months ago #

    @duce: I honestly do think I understand your point and what you're going for. I think the issue is just that we've decided not to allow imports from below wp-content, and that's functionality that was important to you, so we're causing you real pain. But I've outlined our reasons, and the reasons are legitimate. Automattic, by the way, are the people who make WordPress.

    I'm sensitive to disagreeing too hard with you because I know we're causing you pain, but I think it *is* part of our job to do what we can to improve security for our users' websites, at least as far as our plugin is concerned. That applies even if people aren't using ideal security practices (indeed, a large percentage of users aren't, so we really have to take that into account).

    I'd also disagree that moving images to another folder outside wp-content disguises that you are using WordPress. It's very easy to tell a WP website just by looking at the source code of the home page, regardless of where images are uploaded and stored.

    As I mentioned, my goal isn't to disagree with you, and I recognize our decision has real consequences for you, and that you know what you're doing. I'm just trying to underscore why we made the decision in the hopes that you (and others who read this) will understand, even if grudgingly.

    Thanks and best (Erick).

  20. duce
    Member
    Posted 8 months ago #

    Obviously that means the end of the road for me and many other photographers using WP and Nextgen. Pity Photocrati lost the plot trying to re-invent the wheel with changing Nextgen so dramatically. I was quite optimistic starting out. Even considering purchasing the Pro version. Now, unfortunately that is not an option anymore.

    *PS: And I disagree that you can see its WP by looking at the source code of the home page. There are multiple things you can do to hide it perfectly. Most high level business websites running on WP does not show it in the least.

  21. hephoto
    Member
    Posted 8 months ago #

    Duce,

    If you are running un linux server, have you tried to do a link of your pictures folders in the wp-content folder ?

    I did this already for the 1.9.13

    Maybe it will still work on the 2.00.33

  22. mcfester
    Member
    Posted 8 months ago #

    @duce
    How do you have all your galleries outside of wp? My default folder is wp/wp-content/gallery and it can't go any lower from the UI, but I'd also like them outside of wp.

    Theres a fork of v1.9.13 been developed and maintained, I don't think this lot will ever get v2 sorted, I tried installing it again on a test site, crashed the site and lost all the galleries, forget it.

    Try this:
    http://wordpress.org/plugins/nextcellent-gallery-nextgen-legacy/

  23. duce
    Member
    Posted 8 months ago #

    @mcfester: I'm still running v1.9.13 on all those websites. I tested on one website with the new version and it literally duplicated images a number of times to the new stupid folder.
    Even tried editing some of the files in the latest versions to no avail. It just defaults back to this silly way even though it does not change the location you specified in the settings.
    One of the websites do over 2 million hits a month with over 17Gig's of images. They must be insane to think I will give this a try and lose all that hard work of years building it!
    Thanks for the link.. Will check it out. :)

    @hephoto: Nope, run *BSD servers and what you are referring to are symlinks probably? Using a symlink in something like that is not advisable as it might attract a few other nasty things.
    A neatly crafted attack on your galleries just might reveal underlying base system info. I'm not 100% sure, but logic tells me not to try it.

  24. photocrati
    Member
    Plugin Author

    Posted 8 months ago #

    Hi all - we'll think about this some more. I have the sense we're having to make a hard decision here between what's best for security for the many vs what's genuinely needed for a few to accommodate existing working routines.

    I think we've made the right decisions, but if we got a sense that the ability store images outside of wp-content was really that important for a large enough group of users, we might consider changing it back, at least for non-multisite installs.

    In the meantime, it also occurs to me we can provide a specific code patch to those of you who want to be able to navigate from root upward. You'd need to make this code adjustment after each update, so it's not ideal, but it does provide the few who need it with the ability to browse outside of wp-content while keeping better security in place for the majority who don't.

    I'll check into this and get back to you.

  25. Paul Chevallier
    Member
    Posted 8 months ago #

    Dear Photocrati,

    Please really consider giving us (the users) the option to use an image folder outside the wordpress directory.

    For me it's not about people seeing that i use wordpress (they can see that on my website). It's that I have two websites on my domain and want to show images on both those websites.
    With the current limitation of the plugin I need to create two copies of the same image to be able to show them on both my websites.

    It would be great to see an option to allow access outside the WP directory - just the option, so disabled by default, but if you really want it you can enable it (I don't know if that is possible of course, but that would make your plugin secure, except for the users who knowingly choose to enable the option).

    If that option would be available I would only need to have one copy of the image on my server and use that copy on both website while still using the Nextgen Plugin!

    Thanks for at least considering the option!

    PS: Thanks for adding the "Keep images in original location" option!!

  26. photocrati
    Member
    Plugin Author

    Posted 8 months ago #

    Thanks for the additional thoughts/vote, @Paul Chevalier.

    Just a quick update. Right now, after talking about this, we're thinking that we may adjust behavior so that by default it's still wp-content and up only, but give users the ability to set access all the way to the root folder by adding a specific line to wp-config. This would allow us to keep a more secure default while providing an upgrade-safe way to change the setting for those who really want it.

    A developer is looking at this now and I'll keep you posted. Whatever we introduce for this will be in the next update. If you have other thoughts or feedback, let us know. Thanks (Erick).

  27. mcfester
    Member
    Posted 8 months ago #

    Another new feature I don't like about the import folder is after a folder has uploaded theres no notification, just the window that shows the upload closes, it doesn't even give a link to edit the gallery.
    Before the page would refresh and say something like "uploaded folder name successful 12 images - edit gallery", this way if I have to leave the computer during an upload when I return I know where I left off, and when importing many folders its easy to lose track if the page doesn't tell me whats just been imported.
    Anybody else feel the same about this?

  28. duce
    Member
    Posted 8 months ago #

    I echo mcfester's request.. As I'm uploading round 1000 to 1500 images and on average 6 new galleries at a time it is quite important to know where you were working when called away from your pc.

    As for the security aspect: (fresh brain today and less irritated)
    The default where the uploader checks first is "wp-content" correct.
    Now please do check what all you see where you can traverse using that uploader. "plugins", "themes" , "all other plugin upload directories".
    And you are trying to tell me that is safe? What if any or one of those themes or plugins have a security vulnerability in them?
    At least when you start in a folder in the root of your website there is nowehere else to go, at all.

    Thanks for considering and yes I think adding a line to wp-config is the way to go with this. Really only advanced user will be able to do it and I am quite sure most will be happy with it.

    As for making it easy/secure for the majority.. Just this week I had long chats with two web developers that without me saying anything talked about how silly nextgen has become and they not using it in future developments.

  29. photocrati
    Member
    Plugin Author

    Posted 7 months ago #

    All - We've made available the possibility to import from above the /wp-content/ folder with our latest (beta) release.

    Please see this page: http://www.nextgen-gallery.com/nextgen-gallery-latest-beta/

    You will need to place the following anywhere in wp-config before:
    /* That's all, stop editing! Happy blogging. */

    define( 'NEXTGEN_GALLERY_IMPORT_ROOT', dirname( __FILE__ ) . '/' );

    Thanks!

    - Cais.

  30. duce
    Member
    Posted 7 months ago #

    Great! Thanks! Now you moving in the right direction. :)

    Just tested it on one of my smaller sites with 18 galleries and found a bug though.

    When you upload images into a folder that has a space in between then NextgGen automatically changes the path from "New Folder" to "NewFolder" in the database reference/link to images during importing.
    However when you check the gallery path when in Manage Gallery it still shows the path where images are: "New Folder". This can not be edited though. When you browse the image gallery then the thumbnails won't display and when you click on an image it can also not find the image.

    So I went and edited the path on the server side to "NewFolder" and the images and thumbnails displayed correctly.

    However, after that, when using Singlepic in a post the image does not show. When you click on the image it does show the image in the lightbox pop-up.

    Also when you edit the gallery and click on save NextGen then automatically creates a new folder "New Folder" as is referenced in the original path and also creates a sub directory in that folder "dynamic". None of these folders contain image files in them.

    As a quick fix I simply edited all references of "New Folder" to "NewFolder" in the database itself. This fixed it for now.

    Please let me know if you need me to test anything else please.

    And thank you very much for listening to us and adding this functionality. You have definitely retained me as a client. Soon as this is polished up and I successfully switch one of the bigger sites to the new version will I buy the pro version. :)

Reply »

You must log in to post.

About this Plugin

About this Topic

Tags