FWR Media

I in Index is uppercase which is incorrect.

Which modification? I don't remember one for product_info.php Re u modifier nope just include upper and lower case.

@@cramli I understand it must be very hard when reading instructions that are not in your own language .. keep going :) Ok let's take this step by step 1) [TEST] Is KissER installed properly take a look in [root/catalog] /errors/ Is there a file in there? if there is does it contain errors? Stay with me though .. if you go offline I won't be able to help.

@@cramli You need to read a file in the download ( using_kiss_error_handling_debugging.html )

On the line above the error print the contents of ( Usu_Main::i()->getVar( 'filename' ) )

I didn't understand the question, what's not working exactly?

Hi Erik Glad the upgrade was easy for you .. KISS by name KISS by nature :) Not sure what was going on in my mind with the name change and I understand it would have created confusion. Well it's great that the stock system offers meta tags and canonical elements now but it doesn't .. yet .. match the functionality of KissMT. Once 2.4 is more "obvious in its nature" I will probably modify KissMT to add to the osCommerce module system as opposed to replace it. Or I may even push a mod through GIT to see if it can become a part of the core system .. god forbid :)

If anyone is struggling with transparencies could you please try the attached and post here your findings. If you try this new file be sure to delete all current thumbs in the thumbs directory otherwise you will just see the old versions .. also hard refresh the browser as the old images may be cached. The attached file replaces: - catalog/includes/modules/kiss_image_thumbnailer/classes/Image.php Image.php

@@snights Well the image you sent worked at my end. I have however done some work on transparencies. Send me your email and I'll send you a new kiss_image_thumbnailer/classes/image.php to try out.

@@aliasmatias This seems to be a conflict of concepts. Prior to USU5 multi language, in order to have multiple languages you would have needed to set up a different shop and domain for each language. The whole idea of USU5 multi language is that you can have one domain and one shop yet offer pages in multiple languages with each page having a language specific uri.

@@snights PNG works fine my end but i want to do some transparency testing .. could you send me a large image example that "doesn't work" please,

You are entirely correct .. a very bad option .. code with errors should be made error free or removed . . any other option is folly.

@@Ps4Life That code uses a function called mh_image, KissIT uses tep_image. Quite simply if tep_image is used and the relative image path exists and height and width are numeric then KissIT will generate an image. You need to look at this mh_image code.

@@Juto That doesn't make sense, also line 183 is the end of the method not the line you are saying .. the file sounds modified. Also 8192 errors!!!! perhaps it didn't go as well as you think.

There is no reason for any conflict .. unless Mailbeez have been daft enough to use the class name of one of the SPL classes.

@@hardikbaweja There are different versions of rewriters for IIS which work in different ways so I have never taken the time to attempt writing for them all .. e.g. URLRewriter IIS rewrite ISAPI_Rewrite Ionic's Isapi Rewrite Filteretc etc. Helicon Ape looks to be the best as far as i'm concerned as the syntax is designed to match apache mod_rewrite almost exactly.

@@fgwapo you would need to modify aPage_Modules::linkTextParts()

@@fgwapo The character conversion files must be named exactly the same as the osCommerce language. E.g. if you had includes/languages/spanish/ And the character_conversion file was named espanol.php then it won't work. Also ensure that the character conversion file is saved as the correct charset.

This was the old development thread .. see my sig for the support topic. USU5 is nothing to do with keywords or descriptions.

@@mafiouso includes/functions/database looks as if it has been incorrectly edited or otherwise broken. I would refactor the complete function from a fresh up to date copy of osCommerce then reapply the KissER code.

@@cfemoca Is your server very restricted? you need to be able to override settings via .htaccess. Try adding the following to .htaccess: - AcceptPathInfo On Aslo PM me a personal link to the site in question so I can test.

Ok but please don't think " my site is fine" because you have suppressed the errors .. your site is broken .. it has 98 errors which need to be fixed.

@@epwork Well it would if yours was standard osCommerce but it's not. It's the includes/modules/config/cart.php that seems to be reporting. I would guess that either this file is run before the KissER code or it is resetting the error handling

USU5 cannot produce a uri like that.

@@bazmlb Please read the instructions fully Add the code from htaccess.txt to .htaccess making sure that RewriteBase is set correctly.