duce
Forum Replies Created
-
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.
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.
And to this day not one single response!
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.Okay, seriously please.
This is a make or break situation for me.If I cannot set the gallery folder to the root folder of the website I have to start looking at using another system altogether. And I have 10+ websites running NextGen. It would be a waste of money purchasing the pro version.
I have just tested in all ways possible to get the layout and gallery and file paths sorted.
My galleries consists of main folders with lots of sub folders.
Example:
domain.tld/gallery/
domain.tld/gallery/Flowers/
domain.tld/gallery/Flowers/2013/
domain.tld/gallery/Flowers/2013-08-09/
domain.tld/gallery/Flowers/2013-08-09/Orange/All image files are uploaded using SCP (like FTP) to the websites. From there the Add Gallery / Images -> Import Folder is used to import the images and it creates the thumbnails.
It however does not create the thumbnails in the folder the images are located but in fact creates a new “orange” folder in domain.tld/gallery/
Please can we give this some priority as I have sites doing over 2 million hits a month and would really love to go for the Pro version with all its nice features such as social sharing.
Could you perhaps include the fix in the subversion version as I update all my plugins with svn update?
Thanks for the hard work. I know you guys are going through a rough patch but I am pretty sure all the new changes will be for the better in future! 🙂
The way I had it setup on the older versions was to have the image title/number displaying above the image and then the description below the image.
The reason for this is that I use ACDSee to write IPTC info to display the title as the image number and the description as a description of the image type and who the photographer is.
When importing the images in NextGEN it automatically imports that IPTC info and displays it correctly.It would be terribly good to have either the image number below/above the image or the image title.
This is utterly important on websites where you want people ordering images for purchase. Many pro photographers use NextGEN to display images that are for sale.Just not allowing to change to root: gallery/
It reverts back to: wp-content/galleryI quickly tried changing this line in file: class.nextgen_settings_installer.php
$this->_local_settings = array( 'gallerypath' => 'gallery',And it seems to kinda work.
However importing folders it defaults to import files from: plugins, themes, uploads.Forum: Plugins
In reply to: [WP Twitter] ERROR~~C1Issue solved. Thanks very much! 🙂
Forum: Plugins
In reply to: [WP Twitter] ERROR~~C1Same problem.
Whoa there!
There is no request token for this page. That’s the special key we need from applications asking to use your Twitter account. Please go back to the site or application that sent you here and try again; it was probably just a mistake.
Forum: Plugins
In reply to: [WP Twitter] [Plugin: WP Twitter] Can't oAuth my twitter accountExact same problem with me.. No request auth being submitted to Twitter.
Run latest versions of everything.