I was not referring to you, but to the guy who insulted a lady like DV.Quote:
Originally Posted by tpeck
Printable View
I was not referring to you, but to the guy who insulted a lady like DV.Quote:
Originally Posted by tpeck
I don't want to buy into another man's argument - I have enough problems trying to get you to understand my own - but I do understand that chap's frustration, whether or not he is right or wrong.
If you have ever had your server hacked you will know what I mean (and, no, it wasn't my fault at all). He is perfectly right not to install a program that may compromise his security - and still has the right to discuss the add-on.
I'm no security buff, but given that you write the filenaming issue has been referred to *thousands of times* in this thread, and you don't therefore think it useful enough to refer to it in a readme file; well, even taking into account your propensity for exaggeration, the illogic of your reasoning tends to make me sympathetic to another poster meeting with similar defensiveness.
When customers write to me with problems, the first thing I try to do is make them feel comfortable - that isn't happening here.
You seem to be addressing some of these server concerns in the update so he wasn't exactly wrong, was he? And neither I believe am I. I don't claim to be an expert - or even right - but even Microsoft appears to have addressed bracket filename issues with Excel 97 in the year 2000.
I politely suggest you are on the wrong track in the communication stakes if you think that having thousands of people write in about filenaming issues means you don't have a problem or an obligation to flag this in the readme file. Or perhaps you would like to give me back the day I wasted on this.
No, but it works for you as you say, so why care?
A tip in article 58 in the Tutorials/FAQ section does advise not using certain symbols in image filenames.
Quote:
TIPS
It is wise to NOT use the following symbols in your image filenames: + [ ] $ ' " \ / ()
Also zen_href_link('', '', 'NONSSL') is not unique to IH2, it is used throughout Zen Cart in various files.
@Diva
One small thing I have noticed with 8c that doesn't break anything per se, but will send a newbie scampering to claim bug.
I am speaking of 1.3.9e new install with no mods. In the 8c load, there is no style_imagehover.css loaded to the classic template. I know that template customization should be done elsewhere but we see sites every day that are modified using classic.
For some reason, IH2 will not work correctly using the 1.3.9e classic template without the style_imagehover.css in the classic/css folder. The install goes smoothly, but a hover over the image results in a shifting down of the entire site. It shifts the height of the image that IH2 is wanting to display. This jump moves the image you were hovering over down as well so that the larger image does not appear anywhere on the page. The user is left with a large blank area running the width of the page and above the header.
If you move the cursor back down to the image, its larger version shows up in the upper left corner of the browser.
If the user doesn't think to move the cursor, they will only see the shift and no larger image. This could create a lot of false bug reports.
Seems simple enough to add classic to the templates folder and style_imagehover.css in the css folder.
Hopefully I've explained this well enough that someone else can verify.
THANX for all your team's work.
In fact I have recommended that DV include a line in the readme about avoiding special characters.Quote:
Originally Posted by tpeck
I think that a one-liner is enough to address the issue.
Regarding the chap that feels entitled to write hogwash about a contrib he doesn't use: I also have the right to describe his rants as what they are.
Wondering if you can read at all...Quote:
Originally Posted by tpeck
...meaning?
Quote:
Originally Posted by DivaVocals...
This version should fix the following issues:
Watermarks on large additional images
Issues with some hosting configurations not setting the file permissions of the bmz_cache child folders correctly
Haven't I been saying this all along?Quote:
In fact I have recommended that DV include a line in the readme about avoiding special characters.
I think that a one-liner is enough to address the issue.
Wondering what your problem really is.
Why not be helpful without the attitude, like clydejones?
You are correct. There is no specific "classic" template folder at all in the Rev8c fileset (as in other mods). There is however an includes/templates/YOUR_TEMPLATE folder, and clear instructions in the readme to rename the YOUR_TEMPLATES folder to the same name as the template folder. This would apply to those using the classic template as well. There are lots of other mods that do not have a specific "classic" template folder, and simply require that those using the classic template rename any template specific folder for the mod to "classic".
From the readme
IH2 will not work correctly for ANY template without the proper CSS or JS files in place. This isn't an "issue" that applies to those using the classic template.Quote:
Rename the includes/templates/YOUR_TEMPLATE folder to your template name.
Quote:
Originally Posted by dbltoe
Exactly.. And there are COUNTLESS articles on the internet that say the same. In fact I'm fairly certain that the error that crops up from the improper naming of image files would be an issue with additional images even if IH2 was NOT installed.
Ckosloff and I talked it over, and as he indicated we did add the same line from the Zen FAQ to the IH2 readme. ckosloff is right though.. The readme is already super long and though it contains lots of good information, it's is not read fully as is. We will still have those who have not read the readme or the Zen Cart FAQ who will continue to use special characters in their image file names, and will run smack dab into the additional images error.
Additionally I am of the opinion that "fixing" the IH2 code to allow for these symbols to be used in files names is an inherently BAD idea. Perhaps some of the developers who post here could weigh in on this thought.
Quote:
Originally Posted by clydejones
Indeed.. The error that is caused by this incorrect naming convention is NOT unique to IH2 at all.. It has cropped up in other places as well..
Quote:
Originally Posted by clydejones
Well, yes, that's a pretty safe bet. No readme file is ever read in full by all.Quote:
The readme is already super long and though it contains lots of good information, it's is not read fully as is. We will still have those who have not read the readme or the Zen Cart FAQ who will continue to use special characters in their image file names, and will run smack dab into the additional images error.
But how is this supposed to obviate your need to write a Known Issues paragraph to help those who DO read help files?
Or are we supposed to miraculously come upon the information bedded deep in a Zencart FAQ file?
OK, well I missed it. Please show me where it was added. (BTW, this totally contradicts what Ckosloff wrote earlier in post #5581.)Quote:
and as he indicated we did add the same line from the Zen FAQ to the IH2 readme