Support community for TTG plugins and products.
NOTICE
The Turning Gate's Community has moved to a new home, at https://discourse.theturninggate.net.
This forum is now closed, and exists here as a read-only archive.
You are not logged in.
Hi Francois,
It's set in the Web Module here:
Change that value, export a new gallery, replace http://francoisgauthereau.com/ttg-be/te … -template/ with the gallery.
Hi Francois, is this the gallery we should be looking at:
http://francoisgauthereau.com/galleries/magalie-et-cedric/index.php
If so, the same issue as before applies.
I see that your Cart URL is set to:
http://localhost:2/ttg-be/cart
Try setting it to:
http://francoisgauthereau.com/ttg-be/cart/
Hi Francois, I see that your Cart URL is set to:
http://localhost:2/ttg-be/cart
Try setting it to:
http://francoisgauthereau.com/ttg-be/cart/
We've interpreted that VAT needs to be collected for digital purchases sold from non-EU countries to EU countries. I'll ask Matt to chime in on that.
Wolfram, is it necessary for you to pick which countries require VAT, or should it be a set list of countries for all TTG customers in the same situation?
Hans, rather than a new state, the way I have planned to do this is to add a new column to countries named something such as 'is_eu', which would be set to Yes for those 27 or so countries. VAT would then be calculated into any sales that originate from one EU country for sales to another EU country. We would then need to also capture the customer's country prior to checkout.
From your understanding, can you help with these questions:
1) Is VAT the only tax you would need to collect? i.e. is there also an additional Sales Tax for sales to EU customers, or for sales to non-EU customers?
2) Do the rules for VAT tax collection apply the same to both digital and physical items?
On a side note, another feature that European customers have requested is back-calculation of tax. (so for example, a 10% tax on a $100 item would be calculated as 9.09 giving you 90.91 after taxes paid). Would you find this method useful in general and in particular in regards to the VAT changes? This change is already ready in my code.
Hi Hans, I was asking Wolfram however I really appreciate any input on this matter
If I understand you correctly, would your second option consist of a VAT amount that affects sales from any country to any EU country? In that case I would have to see whether the existing 'Sales Tax' field would still be useful for other countries. For example, would a photographer from the US charge both Sales Tax (to be paid locally) and VAT (to be paid to Europe) on an order destined for the EU. This is where it gets complicated.
We don't sell many carts, so I can't justify spending a whole lot of time on this. So I'm looking at finding a solution that best meets the needs of customers in the EU with a reasonable effort.
Bluehost should set the ownership of the directories to your own account. In my case, everything is owned by 'somexxxx' (where xxxx is the rest of my account name).
galleries/custom-thumbnails should be a directory that you create via FTP, and therefore always writeable by you. This is not the same folder as custom_thumbnails found within each album. Any image placed within galleries/custom-thumbnails can be used as the cover image for any album.
What's your preferred solution?
Hi Hans, we're looking at handling some kind of support for the new VAT regulations, though not in the way you've described. Since the VAT rules are overly onerous, and require the collection of data beyond what the Cart can offer, we're looking at providing a setting to prevent sales from one EU country to another (or also from a non-EU country to a EU country).
Would this be of benefit in your case, or do you have a significant portion of sales from other EU jurisdictions?
I imagine that capturing a VAT-registration number would require the Cart to verify that it's a valid number that matches the details of the customer. Again, do you see a significant portion of your sales falling into the scenario of VAT-registered customers from other EU jurisdictions?
The metadata handling code does have the odd issue that rarely comes to light.
Can you post the metadata tokens you are using, if any?
Also, are you publishing multiple albums in parallel?
Hi Peter, Matt has covered this here:
http://theturninggate.net/2011/12/disab … text-menu/
Though it's best to leave it to the professionals I'll remove those albums this evening. I suspect there is still an underlying issue in albums not being removed automatically in the database.
Do you want me to go ahead and remove those two galleries?
Something strange is going on here. The duplicate album, Katherine, and Katherine Headshots galleries all have empty slugs in the database. The only scenario I know of that should cause slugs to be empty is to attempt to use the Default Album. Clearly this isn't the case here.
Are the files for Katherine and Katherine Headshots albums still on your server? You should be able to check by looking under proofs/ within your FTP program.
The best way to look into this issue would be via FTP. Can you setup FTP access for me and message me the details?
Please provide a link to the gallery with login details if password protected or CRG-managed.
Hi, I have moved aside the duplicate album. For that album, had you attempted to use the Default Album that Publisher creates automatically?
Which album/s are you seeing that should no longer be there?
When prompted to delete the album, did you click Delete or Leave on Service? The latter will keep the albums on your server.
Thanks for the login. Please provide the URL of your website.
Here's how it works:
Standalone galleries
1. Client visits page gallery. The CRG created a temporary session ID that ties the currently viewed album to the database.
(2. Optionally logs in through standard gallery password protection.)
3. Provides feedback per item. This saves the feedback in the database associated with the temporary session id. At this point the feedback is only saved for technical purposes. We don't know who the client is, and the feedback session is incomplete (not submitted) so not available for viewing in the back-end.
(4. Optionally, client reloads page, or changes pages in the gallery. Feedback remains in page. If client closes and reopens window, the session ID is lost, and we're back to step 1, as though visiting the gallery for the first time.)
5. Client submits feedback. Personal details are provided, and matched to the previously entered feedback. Emails go out and you're able to view the client feedback in the back-end.
It's important to note that feedback will be lost if the client closes the window before submitting feedback. This is expected behaviour of interaction with web browsers.
CRG-managed galleries
1. Client visits page gallery. Client is redirected to CRG login page.
2. Client logs in. Redirected back to gallery
3. Provides feedback per item. This saves the feedback in the database associated with client. The feedback session is incomplete (not submitted) so not available for viewing in the back-end.
(4. Optionally, client reloads page, or changes pages in the gallery. Feedback remains in page. If client closes and reopens window, the login is lost, and we're back to step 1, ready to login again. If feedback had previously been entered then this will again be visible in the gallery.)
5. Client submits feedback. No need to provide personal details as these are already matched in the back-end. Emails go out and you're able to view the client feedback in the back-end.
Alternative CRG-managed login
1. Client visits ttg-be/crg/
2. Client logs in
3a. If only assigned one gallery, redirected to that gallery
3b. If assigned more than one gallery, directed to a list of assigned galleries
I'm not sure about genius, but I'm glad to have been able to help
It's time for sleep down here in Melbourne. Wishing you a great day.
Hi Sanne, I can see your changes after clearing my browser cache. It should work for you after clearing the cache.
That modal.css file is common to all galleries that use the cart, so the fix should apply to both /sort/ and /tester2/
Hi Sanne, a quick fix would be to change the max-widths in the file /ttg-be/cart/lib/css/modal.css
Specifically, the max-widths for #modal and #modal .details would need to be increased. These are currently set to 640px and 469px respecitively. Increasing them both by 150px seems to work well, i.e. to 790px and 619px
(FYI, the two width lines mentioned above are on lines 6 and 58 of modal.css)
For a longer term solution, take a look at Custom CSS support, documented here: http://ce4.theturninggate.net/docs/doku … custom_css
Technically, all feedback is stored on the server, for each interaction of a gallery irrespective of crg-managed or standalone. However there is no function to view any of that feedback until the feedback has been submitted.
That is not how CRG works. The model is: client visits your gallery, completes feedback, submits feedback. You view the feedback for an album. By hiding the status bar you are breaking the functionality of the gallery.
Hi, I've had a look. What I can 'see' is that the status bar, which includes the submission link, is invisible. The items are there, but not shown. I was able to submit feedback by clicking the right-most clickable area. Did you receive the test submission that I made?
Matt will probably need to look at this to advise on why the icons in the status bar aren't showing.
We've solved the problem. For others that may stumble upon this thread:
A very few hosts require PHP files to have the permissions of 755, instead of the usual 644. Publisher has a facility to set the permissions to 755 at the time the albums are created. To use this, add the following line near the top of ttg-be/publisher/index.php:
define('FIX_PHP_PERMISSIONS', true);
So that the top few lines look like:
<?php
define('FIX_PHP_PERMISSIONS', true);
//$start = microtime(true);
if (!defined('APP_DIR')) {
define('APP_DIR', 'application');
}
None I'm afraid. This is a fairly obscure use case and I have a tonne of high priority tasks I'm working through.
Hi, 500 errors are difficult to solve. Try to see if there is an error log somewhere on your server, perhaps under public_html, or under 'logs'. That may include the underlying error. Failing that, please provide an FTP login that I can use to work out the issue, by sending it with the Email link under my name.
Something to try: have you used 777 permissions on ttg-be/data or galleries? If so, try 755 instead and see if that solves it.
Also, are you using your own phplugins? If so, try disabling that.