Jump to content
Latest News: (loading..)

toyicebear

♥Ambassador
  • Content count

    6,339
  • Joined

  • Last visited

  • Days Won

    36

Posts posted by toyicebear


  1. It's interesting to have the product information shown in a modal window instead of a normal page. It allows to quickly return to the list of the products previously seen without hitting the back button and having the page load again. Hardcore shoppers can close the modal window with the ESC key :D Again, interesting concept.

     

    Such a feature would be better as a user optional choice, ie. by having a quick info button/icon they could click, while clicking the image or title would bring them to the product page.


  2. I see that people are talking about Ultimate SEO URL I'm not sure if this is what I need. I can find information about but I don't what the cost is and where to get it.

    I want search engines to find my store and website and get better placement will this module work for that.

     

    You can find Ultimate SEO Urls and much more in the add-ons section of this website. The add-ons are free.


  3. Would a procedure like this not make sense?

     

    1. Once someone enters the website a cookie is attempted "set".

     

    2. When someone initiates an action (add to cart, change language/currency) at the website the session is started and a check is run for the cookie and if it exist then use cookies for the sessions if not then append them to the url.

     

    This would make it so that the risk of someone "copies" an url with session id attached would be minimized since no session id would exist for most visitors(guests) , only for those who had cookies set to off and also have initiated an "action" on the website.

     

    Security wise more checks could be added too if wanted/needed like checking the session id against ip and browser id so that that even if someone copied an url with session id attached they would not "hijack" another persons session.


  4. Most add-ons will require you to do manual code edits. You will need to download the "mentioned" files to your local pc via your hosting control-panel or a ftp program.

     

    Then you can proceed to edit the files using a text editor like for instance Crimson Editor, Notepad+ or similar

     

    Then you can re-upload the files again.

     

    If you are asked to do any DB changes then that can be done via PHPmyadmin which you should be able to access via your hosting control panel.


  5. Cookies have always had, and probably always will have, a bad reputation. Some people still do not use them, or have their browser/firewall set to limit them. I get requests fairly often from shop owners asking how to fix a problem a customer has complained about - the problem being the cookies required message. Some shop owners take the opinion that cookies are fine and if the customer doesn't want to use them, tough luck. In my opinion, the chance of losing a single sale because your shop forces a customer to change how they prefer to surf is just madness.

     

    Outside of what this topic is about, but worth a mention is that the same sentiment also goes for requiring java-script to be enabled in the visitors browser for the shop to function.


  6. If the EU Cookie laws get any stricter than they are today, then relying only on cookies can become an issue at-least for those doing business in the EU region. Imagine having to ask the customers permission to accept a cookie before he/she can add anything to their cart.

     

    But as most of the other carts are requiring cookies and javascript enabled in the browser to work, i guess that is just the way the trend is going. EU and other regions hopefully will take usability on the web into consideration for future "privacy" rules and regulations.


  7. Loginto your account at paypal.com and make sure you have enabled the "PayPal account optional" setting.

     

    If you want to "check" how it will look for your customers, delete your browser cookies before trying. PayPal sets a cookie to enable them to identify who already have an PayPal account and will show a different screen based on that.


  8. That module is very flexible, but you do not need to use all the possibilities it have. You can set it up not to have multiple zones and use as many different flat rates as you like.

     

    Or you can just make a new flat2 rate module based on the included flat rate module...then you can use flat for standard and flat2 for express.


  9. To get Level 4 PCI compliance is not that expensive. BUT you will still not be able to save cc information for later manual processing. You will on the other hand be able to let the customer input the cc date on your site which is then transmitted to a payment gateway in real time online. (Like Authorise.net, PayPal Pro, PayPal PayFlow and so on)


  10. So is there a contribution for v 2.3 to collect the card number so it can be entered manually into an existing merchant account/terminal (without the cvv)?

     

    I know in v2.2 there is a contribution (I think it may be this one) that splits the card # and stores the first 4 and the last 4 #'s in the db and then emails the middle 8 digits, that way the whole number is not stored. Is there a contribution like that for v2.3?

     

    I haven't upgraded to v2.3 yet and I have been considering it the past few days, but I already have a merchant account in my store and getting a separate one just for the osc site doesn't make sense to me (if you are even allowed to have two merchant accounts)

     

     

    Close to any 2.2 module can be made to work with 2.3.1 , but in most cases you dont need to get a new "merchant account" you can simply talk to your current provider and ask them about also using it with an online shop and what payment gateways they are compatible with....


  11. I still think it would be better to give the administrator the possibility of forcefully deleting the customer or not. If the constraint is added at the database level, no such user-end feature would be possible.

     

    I agree. I see no reason to limit the administrators possible actions at the db level, keep such options open and add restrictions/warnings in the code.

×