In several of the "pro viewers only" options for my page, it's not obeying. For example, I've tried to move the gallery title position to "above thumbs", but it's not obeying. Any ideas? Thanks.
26 2015-02-07 15:04:32
Topic: Customize page, "Pro Viewers only" options, many not working [SOLVED] (3 replies, posted in Showkase Support)
27 2015-02-07 14:59:08
Topic: Problems with site heading truncating at some screen mags in Kosel (3 replies, posted in Showkase Support)
Hello Steven and company!
I just switched to Kosel, beautiful looking theme! In your copious free time, feel welcome to design more themes :-)
But back to My site, which is bobsgallery.digido.com, now in the Kosel theme, at most screen widths, the site heading "Bob Katz: Photographer", part of the word Photographer is cut off. If you shrink the browser far enough the entire text becomes visible, or expand it to full size it's fine as well, but most intermediate sizes, the heading is cut off.
28 2015-02-07 11:24:37
Re: Unable to install Showkase (17 replies, posted in Showkase Support)
Dear Steven: I think I figured out the cause of the bug I've described: Database issues. The database identifies a unique folder/nav link by its name and keeps track of that, but when a folder is trashed with a particular name, it is not excised from the database. So if I had previously created a folder with the name "landscapes", trash it, and then later create another one with that name, the characteristics of the previous folder may get put onto the new one. Instead, an approach of a unique id could be used, with a GUID entry inside each folder to identify it.
But regardless, this bug is obviously being aggravated by my workflow. We should start another thread to describe lightroom versus Showkase-based workflows and see if we can decide what's best for a lightroom user. The web module in Lightroom is more "static" than Collections anyway, it does not have specific collection criteria like a collection, so it's pretty lame anyway. I'm now ready to consider forgetting about using the web module and Juicebox pro in Lightroom and instead making Collections, exporting and doing it all in Showkase. I think that would make you very happy and I might be happy, too. :-)
29 2015-02-07 05:16:54
Re: Unable to install Showkase (17 replies, posted in Showkase Support)
OK, I tried the ftp approach and Showkase didn't know what to do, it screwed up its database. But here's another puzzle related. I did a new import, with the result of a folder being named landscapes-2. When it is named landscapes-2, all 8 images show up in the gallery. But when I try to name it "landscapes", suddenly it reverts to having only 7 images, which was the state of the old landscapes folder that existed before the new import. I think this is a bug, related to back button bug I had. Something in the config or the initialization or old data reappears... This means that a new import to a folder which is then renamed with the same name as a folder that previously existed will screw things up. Please take a look at that scenario. Thanks.
30 2015-02-07 04:54:01
Re: Unable to install Showkase (17 replies, posted in Showkase Support)
What would be the best process to update a Gallery that's been tweaked in Lightroom. Perhaps I would add new images, that would be the most common change. I would prefer to do the upload from Lightroom as opposed to importing images into Showkase. But since these would or should land in the "temp" folder... I would have to do a reimport? What would happen if instead of re-import.... through FTP I replaced the contents of the Juicebox gallery. Would that screw up Showkase's database?
31 2015-02-07 04:34:01
Re: Unable to install Showkase (17 replies, posted in Showkase Support)
Well, that idea didn't work. I have to have all folders at 777 in order for Showkase to create a new page, for example.
32 2015-02-07 04:06:50
Re: Unable to install Showkase (17 replies, posted in Showkase Support)
Wait! I just gave myself an idea. I set the permissions for the folder and contents of sktest to 777 but set the permissions of all other folders and files to normal permissions ---- and the compatibility test passes. I wonder if Showkase will work normally still. I'll check and get back to you.
33 2015-02-07 03:59:21
Re: Unable to install Showkase (17 replies, posted in Showkase Support)
So we're down to permissions having to be 777 to make things work with Showcase. I just tried setting all folders to 775 right now, and the compatibility test fails. Since the difference between 775 and 777 is simply that "Others" get write permissions. That's the extent of my Linux permissions knowledge, but I wonder if it's possible to assign the Showkase "app" to be owner or group, then the 775 permissions might work?
Here's the compatibility report when folders are 775:
File handling tests
No base directory restriction.
The test program will now carry-out a few file operations. If these produce any error messages then you should check the permissions on the ‘sktest’ folder and all of its contents and then run the test program again. See the help document for information on file permissions.
Attempting to create test folder g1/…
Warning: mkdir() [function.mkdir]: Permission denied in /home/digido/public_html/bobsgallery/sktest/filetest.php on line 98
Failed to create test folder
Attempting to copy test file gallery.xml…
Warning: copy(g1/gallery.xml) [function.copy]: failed to open stream: No such file or directory in /home/digido/public_html/bobsgallery/sktest/filetest.php on line 103
Failed to copy test file
Attempting to read contents of test file gallery.xml…
Warning: file_get_contents(g1/gallery.xml) [function.file-get-contents]: failed to open stream: No such file or directory in /home/digido/public_html/bobsgallery/sktest/filetest.php on line 108
Failed to read test file
Attempting to open test file gallery.xml for writing …
Warning: fopen(g1/gallery.xml) [function.fopen]: failed to open stream: No such file or directory in /home/digido/public_html/bobsgallery/sktest/filetest.php on line 113
Failed to open test file
Attempting to write to test file gallery.xml…
Warning: fwrite() expects parameter 1 to be resource, boolean given in /home/digido/public_html/bobsgallery/sktest/filetest.php on line 118
Failed to write to test file
Deleting test files …
Warning: fclose() expects parameter 1 to be resource, boolean given in /home/digido/public_html/bobsgallery/sktest/filetest.php on line 123
Problems with some file operations: please check file and folder permissions
34 2015-02-07 03:45:50
Re: Unable to install Showkase (17 replies, posted in Showkase Support)
I did eventually fix the back button bug by by creating a gallery with a new name, other than Landscapes. Let me see if the bug comes back right now if I rename the gallery to Landscapes. Interesting! Now the bug is gone... I won't look a gift horse in the mouth. Teething problems?
35 2015-02-07 03:42:08
Re: Unable to install Showkase (17 replies, posted in Showkase Support)
I have removed browser's cache several times whenever the back button bug came up. As for the import functionality being added as a convenience, I'm very glad it's there. I run a Lightroom workflow, it's my main database, and my goal in life would be to confirm any Showcase gallery to the gallery I first create in Lightroom, choosing images from my database and interactively putting them into the gallery.
36 2015-02-07 03:36:31
Re: Unable to install Showkase (17 replies, posted in Showkase Support)
Thanks, Steve. I'm still reading your reply, but replying "in pieces". I DID run the compatibility test, several times. It only passes when I use 777 permissions on the files :-(
37 2015-02-06 19:10:29
Re: Unable to install Showkase (17 replies, posted in Showkase Support)
Aha! I deleted "landscapes" (which is no longer an active page) from terminal. Now I have a remaining gallery and folder named landscapes 2. In Showkase I change the name to landscapes, which changes the name of the folder and the nav link. Aha!!!!!! As soon as I do that, the old bug with the back button appears.
I think this is a problem with a config file or some other initialization bug. As long as I name my folder and nav menu something other than Landscapes, I do not have the back button bug.
38 2015-02-06 19:05:52
Re: Unable to install Showkase (17 replies, posted in Showkase Support)
Wow.... with standard permissions, Showkase can hardly do anything right.
Now for a sequence of events:
1) All permissions set normally (664 for files, 775 for all folders, starting at the bobsgallery folder which is the root)
2) Folder "landscapes" exists. Want to remove the page to try again, so I choose "trash". It is unable to trash this folder or page. I try to import the Landscapes gallery again from the temp folder, but Showkase reports it is "unable to create the folder landscapes 2"
3) Change all permissions to 777 on folders and files (dangerous, not recommended for security reasons). I forgot to delete landscapes, but anyway I do an import from the temp folder and now it creates "landscapes 2" and furthermore it does it without the nasty back button bug!
So I'm operating (unhappily) with all permissions set to 777 and awaiting your reactions. Thanks in advance.
39 2015-02-06 18:46:23
Re: Unable to install Showkase (17 replies, posted in Showkase Support)
Oh, safe mode is not enabled, and it has not been enabled... just some parameters are enabled. When I make a gallery by import from the temp folder as its defaults, it still has that title and back button.
40 2015-02-06 16:06:19
Re: Unable to install Showkase (17 replies, posted in Showkase Support)
Well, I removed some of the PHP safe mode parameters, and to no avail, so I need more specific guidance. Did I find a bug. Please visit my site which is [disguised here as a true link is not allowed in your forum)
go to bobsgallery.digido.com
Mouse over image and you will see the recalcitrant back button text and a functional link. I can't find ANYTHING in the configurations that include a back button request or a link. This is a gallery imported from a temp folder created in Lightroom. If you choose bobsgallery.digido.com/temp/Landscapes you will see the pure Juicebox version that was originally uploaded and as you can see, it does not have a title or a back button link....
41 2015-02-06 15:32:27
Re: Unable to install Showkase (17 replies, posted in Showkase Support)
While I'm waiting for a forum reply I'm still playing. I was able to trash the landscapes folder from within Showkase. But my system would not allow it to trash the folder Landscapes which was uploaded by Lightroom. I'm going to try the temp folder (outside of the Showkase folder) approach and see what happens.
42 2015-02-06 13:04:49
Re: Duplicate folders (6 replies, posted in Showkase Support)
Deleting folders by FTP is very slow and inefficient. I use Cyberduck and you also have to refresh frequently. If you can SSH to your site from a terminal then the rm -rf command can do the job. But make sure you are really comfortable with terminal use. If you are, it can save tons and tons of time.
43 2015-02-06 12:58:27
Re: Duplicate folders (6 replies, posted in Showkase Support)
Thanks for the idea of the temp folder, Webitect. That's a great idea! Basically, if Showkase is going to copy a gallery into its own folder on import, might as well have a temp folder for the Lightroom upload. What do you suppose is the correct procedure if I use Lightroom to UPDATE a gallery. Should I then delete the gallery from within Showkase and then reimport it?
Bob
Webitect wrote:
Hi Steven,
Thanks for such a prompt and detailed response. Much appreciated.
Thanks for the offering the work around and detailing what wouldn't work if implemented. I pretty much have things the way I want now. I deleted everything and started again because it was too time consuming to try to figure out which folder was the correct one. Lucky this happened with only the 6 galleries uploaded.
Anyways, while waiting for everything to get wiped off the server, I devised a naming convention so I wouldn't have to edit any names once imported and will operate out of a temp folder. I'll just have Showkase scan the temp folder instead of root for importing. If you can foresee any future difficulties I may run into, please let me know.
I need to go get the update now, thanks for the tip!
44 2015-02-06 12:54:16
Re: Unable to install Showkase (17 replies, posted in Showkase Support)
Aha, I see why there is a duplicate of Landscapes in my hierarchy... according to another thread here, Showkase creates a duplicate folder when it imports a Juicebox gallery. I think that's counterproductive, but it does explain what's going on. But what's going to happen when I reupload some changed images from Lightroom? Should I re-import? Trash then import? This really seems counterproductive. I'll continue reading the thread about the duplicate folder and see if there is a better solution.
45 2015-02-06 12:51:07
Topic: Unable to install Showkase (17 replies, posted in Showkase Support)
Dear Showkase:
If I may tag onto this thread --- I'm sorry, it's listed as "solved" but I'm having some problems related to the thread.
I'm really loving Showkase but it looks like I have to solve some problems which I think are related to PHP being too restrictive. Note that I can change my PHP configuration myself, I have full access to the WHM (Web host manager) for my Apache at my service provider, and I can change permissions at will by FTP. And I can read to you any directives which are restricted. My PHP has been restricted by a firewall I installed on my Joomla-based site, which is also running on this web server. So it would concern me to "unrestrict" PHP but the Joomla site is pretty stable at this point and I'm not adding any more plugins, and the firewall already keeps external hackers from attempting to log in and do exploits. Are you familiar with all the PHP directives which are used by Showkase and which ones I should change in the configuration?
When I installed Showkase the fie tests failed. I set the permissions as instructed for the folder containing Showkase and for the files within and it still failed. I set all folders to 755 and all files to 644 as requested but the file test failed. I then upped the permissions for the folders to 777 (which I know is very bad), and the file tests passed. This was a bad omen but I hoped I could move on. And for the most part I was able to. However, I see after Showkase has been operating for a time, some of the folders it has created have reverted to 755, and some of its files are 644. This may or may not be the actual problem. Obviously I can't keep on altering permissions to make things work, we have to solve the problem elsewhere. I hope it's with PHP or else then I've found a bug in Showkase :-(
I'm using Showkase Pro and creating the galleries with Juicebox Pro plugin in Lightroom, and uploading the gallery with Lightroom's FTP feature. All that is working.
My problem is I began to find some attributes that I could not fix in the gallery. The back button is now stubbornly installed though I had turned it off in both Showkase and in Lightroom (just in case). Its text is still there and it is still calling a link that I no longer have configured in Showkase. Then by trashing the gallery with rm -rf in a terminal, removing the gallery from within Showkase.... and then starting all over again from a Lightroom upload and a Showkase import and the back button problem remains. I wasted a few hours playing with the configurations and just could not get rid of the back button or its text, which is sitting right on top of the text for the gallery title within the gallery.
Finally when I tried to trash the gallery from within Showkase it reported "Cannot move page to trash", which I think is a symptom of the overall problem. I know the problem is with Showkase and not Juicebox because if I access the single gallery directly by addressing the gallery subfolder in a browser directly, the back button is not there nor is the problem. It only occurs if I access the gallery through Showkase by addressing the Showkase root folder in a browser.
Another note: My first gallery is in a folder called Landscapes (upper case L). At some point, some mechanism creates ANOTHER folder called landscapes with a lower case l... I don't know what to do about that! Hopefully it's all related to the same PHP issue.