Quote from: Ktools_Jeff on October 29, 2012, 15:22

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.

Quote

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.

If you are looking for software that can compare and merge, there are a lot of free software out there already that can do this. Like for example winmerge for windows, I'm sure there are others.

I actually use a paid one called araxis merge.

Quote from: jsnover on October 29, 2012, 15:06

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.

Yes, that is the issue I ran into Sean.

There have been 2 upgrades to Version 3 of Photostore since I purchased it, including the Smarty update. But I have put so much work into customization that I cannot upgrade, or everything will be wiped out. I don't know that there is any way around this issue.

It's also the reason I chose not to purchase Version 4. V4 does a lot of functions that I wanted, and it just looks a lot better. But I can't tell you how many hours went into the customization of 3.8.8 and I'm not going back to Step 1.

Search relevancy for words is a great idea but what really needs to be looked is searching with multiple terms. If a customer types in three words for example: woman shopping

The first results should be images that include both of those terms.  As it is now on my site I'd get a few dozen images that only have the keyword woman above images that are tagged with all three. This is a major issue. 

Secondly, I am personally finding that customer service could be better with Ktools.  It seems like there is a somewhat defensive approach of "our software is fine, the users are just being picky and/or don't understand."

I get that developers would rather spend time developing new features than dealing with support issues, and probably get a lot of what they consider dumb questions, but in my experience the general tone has been more along the lines of "the customer is probably wrong" than "what can we do to improve." Just some honest feedback.

just popped your question Sean to our webmaster at work- his reply, "Not sure how they set up their database that way. that makes no sense at all. hopefully if keywords are identical ("flower" and "flower") there are not duplicate rows in the database. From a performance issue it shouldn't be too bad if the dbase is properly indexed. but it seems strange to me to have 30K in keywords alone."

just popped your question Sean to our webmaster at work- his reply, "Not sure how they set up their database that way. that makes no sense at all. hopefully if keywords are identical ("flower" and "flower") there are not duplicate rows in the database. From a performance issue it shouldn't be too bad if the dbase is properly indexed. but it seems strange to me to have 30K in keywords alone."

It's not how I did it in the project I was working on - I had a table of keywords, and a table of images, and a table that linked the images to the keywords.

Yes, there are duplicates galore.  A row with "female" for every image that has it as a keyword.  I don't want to attempt to change and rewrite this paradigm, as I'll never get anything shot again.

Although, I guess some table has to have one row per image/keyword pair up.  If it's 50k in one or 50k in another...

I'm ok with "run" not coming up with a search on "running", though.  I more like the exact match.  I've taken out their search for "LIKE '%keyword%'" against the keyword table to be just "= 'keyword'" as I've read wildcard searches are extremely heavy.