Hopefully, they will come up with an improvement for it. I'd probably go out and buy the new version if it had a good improvement to the search. I'm sure I could bolt that on to my existing site.

The image zoom is just an overlay of a bigger preview image, which would be easy to grab:
http://www.realstockphotos.com/samples/NDkxMjZiMDE0OTAwMQ==/MjI2YjAxNDkwMDE=/photo.jpg&size=1024

You don't even have to look at the source code - just right click and view image when using the lens...  More the point is that it isn't a real "zoom" - you can't get closer than a 1024 preview of the image.

It's better than nothing, although the lens does stop someone from right clicking the smaller preview to save as a comp.

The other issue is that the preview image on the page is actually the larger zoomed image, resized via html.

Yeah there seem to be a few kinks to work out on the newer features.  Good news though, there is some search updating underway and Jon posted a preview of some of the changes that will be in 4.1.1 that he says will be released soon.  So things are moving along.

I'm sure I'm going to end up hiring a pro to do more tweaking in the future for things that are over my head in the code department but with a few more of the upcoming features and fixes in place Photostore v4 will be pretty robust out of the box.

Thanks for the heads up. Did you test the update he posted on the forums?

Out of the box, Search does not work and has never worked. As you mention, it will return results for "chairman" if you search for "chair". It also will not recognize simple plurals as being identical to simple singulars. So if you search for "cars" but your images use the keyword "car", your customer will get 0 results even if there are many potential search matches.

There are a lot of requests on the forum for a working Search. I don't think it is much of a priority, as those threads are literally 5-6 years old.

You will need to reprogram the algorithm yourself if you are comfortable in PHP. Or hire someone to do the coding for you. One suggestion I have is to get rid of all of the various choices for search (the different match options) and just go with the one which makes the most sense to a user. Then write the code changes to conform to that match option.

Yeah, I'm quite surprised they aren't prioritizing this.  That have said on their site that other add ons like RM sales is more requested... but if the search doesn't work, I'm not sure any add is usefull.

Another example.

If I search for race car
I'll first get a pile of carpentry images, then some healte care images, then a few pages of scary halloween images, some images of monte carlo, several pages of people in an embrace, and if you're lucky you might even see a picture of a race car

Quote from: cidepix on October 16, 2012, 05:48

Wow.. That's a big issue imo.. I am going to get a new CMS when I have time to work on it and implement it on my other site probably in a few weeks, and this is a good warning.. I will keep an eye on this.. if corrected will get ktools, if not then some other CMS..

It's a shame because ktools looks like a good solution.. but this issue is IMPORTANT..

Your site seems to do it as well. A search for key gives you key, turkey, keyboard.

I am not too happy about that so I am considering ktools for my other site..

the next CMS "if I am getting one", needs to be better than the one I already have..

If I get ktools before these issues are sorted, all it will do is annoy me

My favorite gripe on this front is that you can't search "man" without getting all results for "woman" as well, so the gender refined search is pointless.

I'd suggest coming up with a way to make it easier to upgrade if you do a lot of tweaks to the php.

Sorry for another post right away, but here is something I should ask you guys.

Jon is working on a relevance system for the search this will prioritize the results to where "men" would show top of the list, and things like "women" will show later in the list. Unless you do an exact search then it would have to be a 100% match (men = men, nothing else).

Quote from: Ktools_Jeff on October 29, 2012, 14:52

Quote from: sjlocke on October 29, 2012, 14:39

I'd suggest coming up with a way to make it easier to upgrade if you do a lot of tweaks to the php.

That isn't physically possible. Any time you add code to a file (regardless if php, html, etc..). Then we release a new file, you will have to go back and add your code to that new file.

If you organize things differently - as opposed to having users just edit your files - of course it's possible. Otherwise big code projects would all have to do massive cut and paste jobs every time updates in dependencies occur. And they don't.

Without any sort of scheme for integrating changes, kTools can't really be a platform for users to build on, just something for them to use as is.

Yep, that's my point.  Having to go through dozens of files to find what has been changed or added, and copying and pasting, makes upgrading more often then very occasionally, a true pain.  Because you'll miss something, and things will break, and it will take forever to fix.  Especially since one of your selling points is "easy to modify" or something like that.

Also, a list of files that have been changed by you would be good - that was never populated in the current release.

It is easy to modify (providing you know css, html, php, or what ever it is you need to modify), just not easy to upgrade after the fact nor do we claim that upgrading a customized store is easy. Then again that really depends on how much you modified, if not much then it would be easy to upgrade, if you modified every file then it will be a lot of work.

Well, yeah.  The point is to have a system that allows some sort of easier way of upgrading then viewing two files side by side to see what lines changed and copying and pasting and missing code.

You can view a list of changed files in your ktools.net account where you download the upgrade packages. Log into your ktools.net account, click on the version history / upgrade link under photostore 4 menu to the left. Then on that page click on the "changed files" link just under each package to see what was changed in that package. Althought this list doesn't actually show the code changed like we use to in version 3, it will still show what files were changed for that version.

Yes, I see that "Changed Files" is a clickable link.  Sorry about that.