Support/Comments for Easy 2 Gallery 1.4.0-RC1

Well, you’ve at least established that it is an Easy2 problem since everything works otherwise and can display text within your template.

The large pictures could be the problem, and maybe the .htaccess fix isn’t working? You might want to reduce the size of a couple of the images yourself, load them into a new folder within Easy2, then try calling just that gallery ID to test if it solves the problem. I think you’re putting a large load on the server to resize such large images, anyway. Resolution beyond 86 dpi or so won’t be seen on screen, or did you want a high res image for people to download?

For magic_quotes, if you didn’t get the warning during the Easy2 install, it’s probably already off, but you could check with your host to make sure.

Quote from: brunomunro at Jul 28, 2010, 09:15 AM

Hi
I was wondering if anyone has tried this on Revolution 2.0 yet and if not how much work you think would be required to get it to work. I would be happy to have my developers contribute to allow it to happen.
Many Thanks
Bruno

Haven’t started it yet.
Yes, you can, as long as you keep this public.
I don’t try to take the control here, but I think it would be best if we discuss about the implementation, since I will implemented more features into the RC2, which of course only for Evolution.
This will be important, so when Revolution has an Evolution converter, the upgrading won’t brake the [!easy2!].

Quote from: modnor at Jul 29, 2010, 09:24 AM

- I tried intentionally breaking the code by removing one of the brackets in the "Edit Resource" window, ie !easy2!]. Then my basic testlayout shows up just fine with css assigned colours in the different div´s, and with the text "!easy2!]" in the content area. When I put the bracket back in again (ie [!easy2!] ), ALL content is gone and I´m getting a 100% blank page only :’(

Eh?
That’s really odd.
Did you install a new plugin?

Quote from: modnor at Jul 29, 2010, 09:24 AM

- The note about turning magic_quotes off is completely unknown to me? Is this where the devil lies?

Do you know about magic_quotes?
It usually gives you trouble when handling forms.
Quote from: modnor at Jul 29, 2010, 09:24 AM

- I also assume that easy2 is making all neccessary calls to external scripts, that the html template doesn´t need to include specific calls to highslide etc.

Yes, since it’s been setup by the library’s setting in a file.
Quote from: modnor at Jul 29, 2010, 09:24 AM

Additional info: I see the Module is making a _thumbnail folder in the folder hierarchy. But there are no images inside this folder.

:)

The thumbnails will only be created, when the image is called on the front-end pages, by using the [!easy2!] snippet call, of course.

Hmm... perhaps the file’s extension? this only allows jpg, jpeg, gif, png.

Generally when a snippet causes a white page, it’s because of a fatal PHP error whose reporting is being suppressed. Check the snippet in the Manager to make sure there aren’t any odd <? or ?> tags in it.

YOBEDOBEDOOOO!!!

I got some major improvements going on here!!!

It was the file size that was giving me these problems.

I photoshopped them to below 1 MB in size each, and now it all seems to work!

But I need to work on the .htaccess file so that my future clients won´t run into this.

:D

glad it’s been solved.
so, how big was it?
perhaps i should apply a new enhancement here.

@modnor Glad you got it working!

@goldsky Yes, it would be easier if clients could upload images straight from the files produced by their cameras. Right now, I’m resizing the images for them and was planning to teach them how to resize them themselves. If this was automated from large file sizes, it would save a lot of manual work. My client just sent me a new set of images - some are small, but the biggest one is about 4.5 MB. Would this affect pageload times at all for the site? I’m assuming that once I view the gallery on my system, the resized images will be created and cached, so there’d be no effect for users? (or Google, who measures pageload time now...)

The images that was breaking my system were all between 3 and 4 MB each. But I´ve been working on localhost all time long, until I would start to get reasonable results from MODx

Donnow whether localhost vs a live site makes a difference in this case

8)

There are several places on a given server where uploads can be limited, from PHP to Apache itself.

I will not be able to make a direct connection between E2G and your Cannon/Nikon.

I have a (amateur) photographer background, I know about this.
For a digital pocket camera, the size of images is related with the system settings, but mostly it’s around 100 Kb (small pixels) to 4Mb (highest pixel).
For a pro camera, the size can arise up to 15Mb, depends on each of cameras’ resolution, which if I’m not wrong, the latest EOS one can have 10 Megapixel.
And I had a work which preparing an areal-site-mapping, which each of the images was more than 30Mb.

We can not make the fully automation, because of like Susan said, this gallery runs on MODx, which runs on PHP, which runs on Apache.
While we need to always make this gallery suitable to the general server’s settings, some of the hosts like to set any significant limitation to their servers, like disabling the set_time_limit(), or enabling the magic_quote.

So, you’re right k4satin, the recommended pre-uploading action is always set the images dimension as maximum equal to the monitor dimension, not a billboard size.

What I said about an enhancement, actually was an additional warning to such of the situation, not a new process.
The easiness of the Easy 2 Gallery, somehow has the limitation from the external environment.

Obviously file size is a real problem here

Suggestion: How about an appropriate warning if the user is trying to import files larger than a set limit, ie 2MB?

In addition an easier-to-see-than-present info about file size could be available, ie at the file upload page itself. The present one is kind of hidden.

:)