Jump to content

GemRock

Members
  • Content count

    2,020
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by GemRock

  1. GemRock

    Sage Pay Form V1.1

    i am sorry but i dont recognise any of the issues in your posts. protx form is the most easy, reliable payment module I have ever used. the only time consuming bit would be to customise the look & feel at protx server so that it look a bit like the shop but that have nothing to do with functionality. i haven't tried any of the new sage pay module as yet. reason being the golden rule: dont fix it if it aint broke. dont even bother "upgrading" (referring more to paypal modules - some "upgrades" are done by idiots and sone only apply to a particular store). @John: wonder if its possible to have an test account (some sort of paypal sand box) to test the new sage pay modules. not a good idea to use clients accounts to do tests on test server, which would be seen as abused. Ken
  2. GemRock

    Sage Pay Form V1.1

    John No. not completely integration cost but also, and more importantly, the over all cost. I believe most shops rae run on a shared server and as such, so far I havent seen any host is willing to, or finds it possible to do pci compliance on a shared server. pci is required for payment methods like protx/sage pay direct, or is it not? which is why i recommend form and never even mention the other two to shop owners since i know itd be a waste of time to discuss the other two. of course, there will still be shops that prefer to use direct as can be seen on the osc forums. so to have the other two modules ready to go would be handy. Ken
  3. GemRock

    Sage Pay Form V1.1

    forget about protx/sage server (not even protx/sage direct), most shop owners would choose form due to cost consideration. if a shop could afford server then s/he would propably not have the time/interest coming here ask questions and fixing issues her/himself. or is it protx/sgae Server is now much cheaper? if not, i would say focusing on sgae form to make sure it works as it used to as protx form. Ken
  4. GemRock

    Sage Pay Form V1.1

    IMHO, your comment on the payment modules may be misplaced. 1. paypal ipn's behaviour of logging every order whenever it comes to the confirmation page is a defect NOT an advantage. a good payment module or payment processor such as protx or sage pay would not need to do this; 2. in my past few yrs experience of impletmenting protx module i can say protx is quite reliable and do not have any of the problem you describe in your posts. in fact shop onwers are quite happy with it; 3. some of the issues described in your posts make me believe your shop could have some problems itself, you could argue that why paypal have no problem, well paypay bypass some of the osc scripts like payment_process.php which other payment modules rely on. if there a problem in that file (or some others) then that would not affect paypal but do affect protx or sage pay. Ken
  5. GemRock

    Header Tags for novices

    its not possible for me to offer further help on this forum w/o looking at the actual template other than to say that the basic idea is to restore the original header section by killing the template's header interference, which will depend on each template. Good Luck! Ken
  6. GemRock

    Header Tags for novices

    I am afraid you have been wasting your time (maybe mine as well). as far as I know these templates bypass the <head></head> section so whatever you do there simply would be no effect whatsoever. read the first several pages of this support thread, there s some people successfully do it with template system. have a look to see if any applies to yours. Good Luck! Ken
  7. GemRock

    Header Tags for novices

    let me first to try to understand you problem: you only have problem with the title meta tag on the product info page(s). if thats the case then post you Title meta tag. below is what I put in as the title tag for the products_info.php I currently working on: <title><?php echo $header_tags[title_tag]; ?></title> That shows the category where the product is in and the product name as the page title. if you only need product name, then comment out this line in application_top.php: if (strlen($categories['categories_name'])>1) $header_tags[title_tag] = $categories['categories_name'] . ' ' . $header_tags[title_tag]; Ken
  8. GemRock

    Header Tags for novices

    Hi All Any question should be posted here. Do NOT pm or email me unless you wish to pay. Ken
  9. GemRock

    Header Tags for novices

    a 5 minutes work if i personally get my hands on it and if i have the time (possibly yes for 5 minutes). Ken
  10. GemRock

    SEO and meta tags

    well, as the saying goes, easy come easy go. easy install easy get rid of in case you change mind. but hard to install hard to get rid off and you may have to live with it becasue it could be too much for it to "go". surely its your call! Ken
  11. GemRock

    Header Tags for novices

    How? are you going to travel all the way down to London to see it on my computers? I have tons of them :) you just need to download a copy of osc2.2RC2a available on this forum - solutions - downloads. on the other hand you already saw it in the instructions - I have quoted the relevant parts of the file in the instructions. Ken
  12. GemRock

    Header Tags for novices

    so am I. Ken
  13. GemRock

    Header Tags for novices

    and rather, what index file you are referring to???
  14. GemRock

    Header Tags for novices

    you not only have one title tag but TWO title tags, which is wrong. you can search the file for the word title and you should find all of them. alternatively, paste the FIRST 60 lines or so of the index.php here beginning from require('includes/application_top.php'); and dont say you can't find that line of code? Ken
  15. GemRock

    Header Tags for novices

    are you using a template? and what is the template? the instructions are for standard, non-template osc shop only. if using template, read the first several pages of this thread there is instruction on how to do it on certain template, which may help. Good Luck! Ken
  16. rather than spending days figuring out someone else code, a work around may be a better solution: switch (language_code) { case "this lang-code": do what ever works for this language; break; case "this other lang-code": do the other bit that works for that language; break; default: ... } FF may show page whereby IE may not. IE (v8) needs catching up. Ken
  17. GemRock

    Header Tags for novices

    you missed this part of installations: How to use - adding dynamic header tags to your shop. Ken
  18. no.its needed ONLY when it does what it says. when it doesn't then replace problem characters becomes create_problem_characters. delete or comment all but the last line return $text; , return preg_replace($search, $replace, $str); becomes return $str; Ken
  19. GemRock

    Seach Engine Friendly URL Support

    i think you may have been brainwashed by some on the osc forums for a fear that does NOT actually exist. you submit sitemaps to SEs and then they would just following the urls on the sitemaps to crawl your site. Google or any other SEs will NOT come to test or type (can they type?) different URLs to see if you got "duplicate" content so that they can "penalise" you - it is NOT to their interest to "penalise" anyone - their job/interest is to find contents that people may be interested in searching, which is their lifeline. if a human surfer are so bored that s/he kills her/his time typing different combinations of urls, well, the only loss to you is just a little bandwidth, and thats all. on the other hand, if one is stupid enough to submit different URLs all of which point to the same page/product, then google would see it as a deliberate attempt to mislead trying to gain higher PR than it actually deserves, in which case the site in question not only gets penalised but may also be completely removed from google index, and, only then, you are in big trouble... Ken
  20. GemRock

    Header Tags for novices

    1. a number of reasons could cause this type of 500 error; w/o looking at the site & the files, gard to say exactly what may go wrong; only takes a minute for an experiensed person to determine the cause; 2. this contr. would not cause it unless you make mistake when editing the files; 3. it may help as the error msg suggests to look at the error log (ask host for where it is or if its available) although many times 500 error wont be recorded in the error log if not caused by a line of code. 4. lack of details what exactly you did: did the site work OK prior to this contr.? what exactly you click and where you saw this error? 5. if error occured immediatly after installation of this cont the it may be right place, otherwise wrong place to post your question Ken
  21. i guess you probably need a pre-installer.php to install install.php, and if that does not work then you probably need another pre-pre-installer.php to install pre-installer.php, until you get through it. seriously, chemo's U SEO URLs was famoursly created for idiots with less than 10 minutes at hand. looking for an "installer" is looking for trouble and show how lazy one may be. I have seen a site using an installer to install an addon and manage to wipe out all the original records in the configuration table. Ken
  22. GemRock

    Header Tags for novices

    in that case, what you used as mentioned in your Post #652 should do the job - a very straightforward thing, can't see it would go wrong. Ken
  23. GemRock

    Header Tags for novices

    in the install instructions, there are two options/ways to add the meta tags. use the second one, which I referred to. Ken
  24. GemRock

    Header Tags for novices

    1. for the home (index) page: look for this line: $kws_home_page_default = ""; then change it to: $kws_home_page_default = "put here my favourable keywords"; 2. for the product info page: replace . ' - ' . TITLE : TITLE with ' ' : ' ' and add TITLE just after 'echo' so that it looks like ...echo TITLE . Ken
  25. GemRock

    Header Tags for novices

    the problem did not relate to this contribution. the site just moved to a new server and have some file mis-matched here & there plus some old php 4 function not being compatible with the phpv5 now on the server. but all fixed now. Good stuff sold on the site! Ken
×