Latest News: (loading..)

Jack_mcs

Members
  • Content count

    28,401
  • Joined

  • Last visited

  • Days Won

    101

Everything posted by Jack_mcs

  1. Phil - What I meant is that it is OK to have code like any of the following (only relevant parts are shown). The way I read what you posted is that the first method is the only correct one. Is that correct? I have to admit, I don't pay a lot of attention to html errors since they usually don't cause any problems. I've never had a form not work when coded in any of the following ways but maybe it will break in future doctypes. <form> <table> </table> </form> <table> <form> <tr> </tr> </form> <table> <table> <tr> <form> <td> </td> </form> </tr> </table>
  2. This addon provides an easy method for keeping your database fit. All osCommerce shops require a MySQL database to function but little attention is ever given to it. Just ask yourself when was the last time you optimized your database? Unfortunately, this is a big mistake since MySQL is prone to developing problems. Some are fixed as the database runs but some are not and, over time, these grow and can severely effect your shops performance. This addon will automatically tune-up the database, speeding it up and correcting problems that many shop owners are not even aware of. Here are some of its features: Defragment the tables Optimize the keys Strip the customers tables of old data Strip the sessions table of old data Strip the user tracking table (if present) of old data Remove old credit card numbers
  3. Demitry - Thank you for taking the time to report these issues. Regarding your comment about "how far back to go to remove such records", this is already present. See the settings in admin->Configuration->Database Optimizer. Regarding the other items: That definition is part of the Version Checker addon. I used to include it in all of my addons but it became a job updating them all when a new version of it was released. But I see that I didn't add a note to install it so I have added that now. I was not aware of the above items. They will be fixed in the next version. I'm not aware of a rule that states what the form must surround. This sounds like a W3C error and is not a real issue, that I can see. Regarding the change for FILENAME_DATABASE_OPTIMIZER, you must be using an old version of the addon. Filename references were removed several versions ago. I may have missed one but I searched the files and can't find any. Also, you mention the change is for the Before 2.3 version. Not using filenames does not apply to that version so it doesn't matter if they are used or not, though I did remove the references from there too. Regarding the yellow buttons, I can't duplicate that error and they work fine for me. If you are using an older version they may not work properly - I don't recall.
  4. This should work.
  5. This addon provides a quick and easy way to create a logo. A screenshot is included.
  6. A new version has been uploaded with these changes: Added font support. Added a rotate option. Moved the css to the module file for easier installation. Please note this is mainly a Bootstrap version. It may work in pre-Bootstrap versions but has not been tested in them.
  7. Yes, it works now. Thank you for taking care of it so quickly.
  8. This is the support thread for the new Header Tags SEO contribution. It is based on the Header Tags Controller but is not compatible. Why the new name? There are a couple of reasons for this. First, so much has changed in the code that it is mostly a different package and maintaining it would be difficult if it were considered just an update. But beyond that, a lot of people mistakenly confuse the Header Tags Controller as just a meta tags handler. It is that but has gone beyond that basic function for some time now. So to compare it to the other meta tags contributions is just wrong. And I should say here that if all you are looking for is a way to handle the meta tags of your shop, you should not install this contribution since it is definitely overkill. But when you consider that the keywords meta tag is rarely used by google at all nowadays, I can't imagine why someone would want to install a package that relied on that tag so much. And that is the real reason for the new name. This contribution is the only one of its kind to tie together so many Search Engine Optimization (SEO) tricks, that the new namejust made sense. What's the difference? The following are the major changes (or the ones I could remember) in this new contribution: -> The code is 100% langage compliant. -> Removed the english/header_tags.php file in favor of database entries. -> Fixed a bug introduced in a previous version. A spelling mistake would make Page Control fail in some cases. I only mention this here because it was a nasty little bug I could never locate. So anyone having that problem should consider upgrading. -> Added control options to admin->Configuration. -> Added additional meta tag options. It is doubtful these will be used that much but a number of requests were received for this option so it was added. -> Added an option to view the title and meta tags on the actual web page from admin. -> Added Social Bookmark code. -> Added code to apply mouseover text to the sites logo - unique for each page. -> Added code to have the breadcrumb use the header tags titles. -> Added an exclude list in admin/includes/functions/header_tags.php that prevents header tags code from being added to certain files (like checkout pages). This is because those pages don't need tags and excluding them will simplify matters. -> Added option to Page Control and Fill Tags so that the keywords can be dynamically generated from the pages on the site. Currently, the code only supports single keywords but I plan on changing that. There is an option in admin to only pick keywords that fall within the keyword density settings. -> Added an automatic page add feature. You still have to edit the actual file in the root but that's all. -> Added easy install instruction for STS shops. There is just one change to make and the two contribution work together. -> Added code to have the new features work with BTS based shops. There may be a few cases where an option doesn't work due to how BTS handles the files, but they should be minimal and not anything to cause a great stir. -> Changed how title, description and keywords are built. This should provide more flexibility for those that want that option. Each item has a sort order and is displayed in the string of text based on that sort order. So, for example, the title of a page can contain some entered text, the default title and the category and manufacturers names (if applicable), in any order. -> Added an Un-Install file to completely remove Header Tags from the database. This should make testing and troubleshooting easier. -> Added code to use curl instead of standard php file calls. The code will try curl first and then switch to a file command if it is not present. -> Tested in MS2, RC2, STS and BTS shops. Special thanks to the following for their suggestions: bkellum java roasters surfalot A lot of time went into creating this contribuiton. I hope it proves useful. Jack
  9. It still failed so I tried a different browser - same thing. The file appears to upload but mousing over it shows a message saying it is too large. The attached shows what I see.
  10. Harold - I'm trying to upload a new version of an addon. Its size is 15 MB but there is an error on the page saying it is too large. Is the size limit smaller than the 30 MB stated on that page?
  11. That has nothing to do with the code in oscommerce, or any shop. It is because links like that are considered security hazards to mast, if not all, email programs prevent them from being shown. If you have ever received an advertisement email you will almost always see a statement like, "If you can't view the images..." There are some ways to code an email to have images displayed but it is generally not worth it, especially for an order email. You may want to take a look at the Fancier Invoice addon. It improves the look of the basic email by using lines and shadows.
  12. The time it takes is how long it takes google. They probably scan your site everyday but not all of the pages at once. As soon as they visit one of the pages that has been rewritten, assuming SEO 5 is working correctly, they will change their records. That means all of the links could be completed tomorrow or not until next year or anytime in between. But, as mentioned previously, it's a non-issue and not anything to be concerned about.
  13. Google won't punish you for the duplicate meta tags warnings so that is not an issue. But SEO 5 should be issuing a 301 for the stock url. That may not work with the rewrite method you are using but you should ask in the SEO 5 support thread to be sure. I don't use it so I can't say.
  14. Dan: It may be worth giving it a try for one shop. If it works well the others could be switched. Just be sure to block your site while the database is being copied so you don't lose any data. The remote you saw in cpanel is probably "remote access." That is an option to allow a connection to your database from some other location. So if you have two sites in different hosting accounts, you could have one load the database the other uses. You would need to put the IP of the second site into the remote access section of the main one to allow the connection.
  15. There might be a noticeable slowdown if the site is a busy one since there is a longer distance involved with a remote server. It probably wouldn't be an issue for many small shops. It might make a difference, too, if the remote server was a local one (same host) as opposed to a completely different location.
  16. Dan - I think the main decision for using a different server for the database comes down to cost. I don't know what google charges but whatever it is, it will be more than what your hosting plan costs. There's no real advantage to having a database hosted on a different server other than if the main server goes down and has to be restored. Restores can take several days on a large server so having the database on an external server can allow you to get your site up more quickly. But such problems are rare nowadays so it comes back to whether having that "insurance" is worth the added cost. There is also the question of how available to the other server will be. If it is slow to load, so is your site. Google states that they have software in place to make that a non-issue so as long as that is true, cost is the only issue, that I can see.
  17. I haven't test that myself but as long as you have removed only the display code and placed that line in the same location, I don't see why it won't work. I am assuming there is only one attribute in the list since that is what you mentioned originally. If there are others, or just a select option entry, then you will have to change that code so it uses the correct ID.
  18. Part of the code you are removing contains the id of the attribute so you need to add a hidden field so the code knows to add it. It would be something like tep_draw_hidden_field('id[' . $products_options_name['products_options_id'] . ']', 0);
  19. That ability is built-in. You need to enable the download option in admin->Configuration and then setup an attribute for the product that needs it. The weight of that product should be set to 0.
  20. Yes, it is possible. You shouldn't remove all of the attributes code, only the part that displays the attributes. But it seems you are going at it backwards. Why not just remove the attributes from the products and include whatever it would have been as part of the products description? Doing it your way, should you ever need just one product to display an attribute, you will be in a bind.
  21. It seems like every other question posted nowadays is about how to upgrade an older version of oscommerce and the op usually references the official version. This post is meant to provide a quick reference for how to convert an older shop to the current, recommended, one. First, the version that should be used is commonly called the Bootstrap, BS or Responsive version. It can be located here. One should not use the official version. The official version can be installed via the hosts control panel so it is easy to think that is the one to use - it is not. Since the BS version is not directly compatible with other versions, the following steps will be needed: Install the BS version into a new location Convert the database. See this thread for help with that. Install whatever addons the site needs. You need to be sure the addon will work with the BS version. This thread mentions specific ones but there are many others that will work. If in doubt, ask in the support thread for the addon in question. If you intend to use paypal, then install the Paypal App. At this point you should have a working shop. Test it thoroughly, especially the payment and shipping modules, before going live with it. When you are ready to go live, Mark your current shop as down for maintenance ( a simple index.html file is fine for this purpose ). Make a backup of the current shops database and files. Convert the database to the BS version. Replace all of the files with the new shops files. Edit the configure files so they work as the live shop. Remove the blocking page. If everything has gone correctly, the conversion should be complete.
  22. The index causes the table to treat that field differently. It doesn't track what is in the field. So, no, indexing won't cause any problems. Although, it is possible to over-index and that can cause a slow-down.
  23. We run MariaDB 5.6 and there are not any problems with any of the versions of oscommerce shops on the server. But according to how I read the MariaDB compatibility notes, there may be problems If V 10 is used so I am playing it safe for now and sticking with 5.6. If you switch to it, please post the results here since this will be of interest to others in the coming months.
  24. I don't have definitive answers for either. If no one else responds here you may want to ask in one of the threads for the Responsive version. But myy guess is that Gold will work with 5.6 since the 2.3.4 version before it did. Though it is not a good idea to be using it (Gold) since it is so outdated at this point. Edge will work with 7.0 and, usually, an upgrade to a php version won't break code that will work in that version, I haven't tested it so I can't say for sure.
  25. If there is a directory as part of the image name in the database and it is not correct, you need to edit that product to remove the directory name.