Community @ The Turning Gate

I've had a look at the scrolling issue, and can't see what may be causing it.  From what I can tell, the HTML markup is identical between the first and second calls to open the dialogue.

A work-around is to change the JavaScript file found in ttg-be/cart/lib/js/jquery.ttgcart-ce4.js so that the dialogue is opened twice on each click.  The second opening should just replace the first.  If you're keen to try this, edit this file: www.kristenwestlake.net/ttg-be/cart/lib/js/jquery.ttgcart-ce4.js

And duplicate the line at line 380, so that instead of this:

that.showModal();

you have this:

that.showModal();
that.showModal();

I can email you the file if you're not comfortable editing it.

They are the album titles.  The second line is made up of slugs.  What links are those?  The second line is just text.

Hi Zeesi,  sorry that was failing due to a debugging statement I had added to work out where it was failing.
The change of php.ini, and removal of the statement, has the admin working now: http://yiftachphotography.com/ttg-be/admin/

That's tricky. Do you or an admin with you have command-line access to the server? If so, it may be worth setting ownership of the entire data dir to 'apache' or whatever the username is that the web server runs on.

Hi Rajiv,

I'm glad to hear you're enjoying our software.  It's great to see you put it to good use. Your site and photos look fantastic.

The way the .htaccess file finds the single.php depends on how paths and user accounts are set up within hosting environments.  In your case, the server is not able to locate single.php.  It needs a more explicit location, including the path.  The extra and changed lines in the tweaked .htaccess file provide this information.  The big question is whether these extra lines and passing the path will cause issues on hosts that don't require the path to be added.

The template you've used creates four renditions.  I've removed the need for two of them (photos-for-purchase and photos-for-download), so if you add further photos then it should now be twice as fast.

Hi Tony, sure.  I've sent the access details via a Personal Message.  Look for the 'PM' link on the top-right of this forum to access your messages.

Hi, that's really interesting and helpful, thank you for sharing.

I have used mod_sec during a casual systems admin role.  It is a very good tool, with a huge number of rules for detecting and blocking security risks.  By default there are too many rules, and as GoDaddy has done, some need to be tweaked or disabled to enable expected function of a site or service. 

There is code within TTG BE that works around another mod_sec rule that has caught customers out (that URLs can not be passed in request parameters).

Hi Tony, those files aren't specific to Windows servers.

We've often found that hosts will switch users between Windows and Linux at no cost and with no effort from the customer. It's worth asking.
You could claim that you are not satisfied with their PHP support, which wouldn't be a lie: PHP runs in a non-standard way on IIS. As an example, when our code tells the browser to redirect to a different URL, IIS servers intercept the request and attempt to redirect within files on the server without telling the browser to update the location. Functionality like that flies on the face of the HTTP spec.

There may be a minor chance you'll face issues on a Linux server, but that's the platform we support and we go to great lengths to help customers work through any issues.

Publisher brings a lot more to the table than faster publishing: two of them being the ability to change the design of any number of galleries with a change of template, the ability to add, remove and reorder images without re-uploading galleries.

I can set you up with Publisher access to my dev server if you'd like to try it out.

That is in fact the system your site is on. The giveaway was the style of the error page when I went to an invalid page..

Great, thanks for confirming.

Hi Zeesi, that would be most helpful.  Please send the details to my email via the Email link under my name. 

LJR69, since you are behind a corporate firewall, can I assume that you or your company manages the server?  If so, it should be straightforward to look at the PHP error logs for any errors.  Many servers will not process sites with 777 permissions, as the permissions can be deemed too insecure for the particular environment.  That often explains a complete failure to load a page.
When running with 755, what is it that isn't working?  Can you provide any error messages or screenshots?