Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by burt

  1. I'm sorry to tell you but Frozen (which is a newer version than you have!) went EOL (End Of Life) yesterday. You should update to Phoenix if you want to easily get support from here on out. For the error, consult your host and see what they can get from their error logs.
  2. There are approx 75 Forum Members waiting in the Queue for access to the Phoenix Club - 99% have zero posts and a throwaway email address. 
    I cannot tell if you signed up to spam the joint or if you are a real person interested in Phoenix. 

    If you have asked for access and have waited more than 24 hours, message me with the URL of your shop...or some other way to show me you are not a fly-by spam-whore.

  3. burt

    Steps to Get Complied with Cookie Consent

    No it's not, and thanks for the Spam.
  4. Here you go: https://github.com/gburton/CE-Phoenix#certified-service-providers Both of whom are available on this forum for you to converse with by Private Message. @raiwa @BrockleyJohn
  5. burt

    Lost with version to use

    Frozen is EOL (End Of Life) on Monday. You should therefore avoid it for a new store and as @ecartz rightly says, Phoenix v1.0.6.0 is the de-facto standard of osCommerce; https://www.oscommerce.com/Products&Download=oscom2ce-phoenix-v1.0.6.0
  6. 1. this thread is not for phoenix 2. there is a phoenix club 3. to get a list instead of a grid, set the width of each thing in the display to 12. It is now a list.
  7. Code https://github.com/gburton/Responsive-osCommerce Demo https://template.me.uk/frozen2bs4/index.php Reminders Frozen is still frozen (at bootstrap v3) Admin is still not bootstrapped
  8. burt

    Report of specific product sole and to whom

    Because I like playing board games, I'll message you a .zip file which you can upload to your admin area and then use to download that data. It might work or it might not - no harm in trying - your shop is ancient version of osCommerce unfortunately. Sorry for your loss.
  9. That would not be possible with a core code change in old versions. The old style page requires each module to be 50%, and this is done using a table, where the modules have no influence over the layout. In effect, this type of coding is as old as the Ark as the "controller" is the page, not the modules. Modules are saying: Here's my Content Page is saying: Here's the slot where you are going. In the recent update, I recoded the page and all the modules to give the modules control over the layout. Modules are now saying: Here's my content and here's my width. Jump. Page is now saying: Yes Sir. How high?
  10. burt

    Site quick Find question

    Within the next few weeks, I'll be releasing a Supp Code which does something that would be almost ideal to be refactored into a Filtering system...
  11. burt

    Site quick Find question

    It's doable, bluff it using the SEO keywords search engine. Give it a "code", eg: All products that fits a compact firearm = FITCF. In your product page, then link to advanced_search_result.php?keywords=FITCF That gets very unwieldy very quickly if 1 product needs multiple "codes". And you have many products. A better way would be some way to set up "codes", then in the product addin/editing page have a tab that allows you to assign 1 or more codes. Then have a new page showing all codes and ability to drill down to find what the customer looks for. IE: a filter system.
  12. burt

    Product Attributes Random Order Problem

    Sort Ordering would be a very simple change to add in the product_attributes area. Support a good coder to allow him/her to take v1060 and make the changes, then (if you wanted to help others in the future) give us back the code to potentially add into the Core.
  13. This is a setting in Admin > Configuration > My Store.
  14. So is that file problematic ? Forget the missing backslash, I forgot to backslash it.
  15. What I'd like to do is this; I will log into the Phoenix Demo and amend a file via the define_language I will FTP it down I will attach it here At that point, you can open in your editor a let know what you see...
  16. What's going on? You are amending the file via the admin/define_language.php You are then downloading the file via FTP You are then amending the file in notepad++ At point 3, you see CR and LF etc everywhere ?
  17. burt

    Add download filename to admin orders

    Note, I refer to Phoenix but older Frozen etc should be similar. That data is not grabbed by the Class; https://github.com/gburton/CE-Phoenix/blob/master/admin/includes/classes/order.php#L121-L124 The available data is option, value, prefix, price. That data comes from orders_products_attributes, so we look at that DB table to see if the download is stored there; https://github.com/gburton/CE-Phoenix/blob/master/install/phoenix.sql#L393-L403 It is not stored. It is stored in orders_products_download; https://github.com/gburton/CE-Phoenix/blob/master/install/phoenix.sql#L406 Therefore...you need to join the two tables orders_products_attributes orders_products_download You have an available join, orders_id. You therefore have to (in Frozen) manipulate the SQL in the class file; https://github.com/gburton/CE-Phoenix/blob/master/admin/includes/classes/order.php#L118 to join those two tables and then output the filename in the array. Then manipulate invoice.php to output that extra piece of data. No other way around it. Same for Phoenix, but in Phoenix...there is a new different option; You could Hook into the invoice and show the download details at the bottom of the invoice, using this Hook https://github.com/gburton/CE-Phoenix/blob/master/admin/invoice.php#L106 in a nice table, you could even show how many times customer downloaded it etc.
  18. burt

    Error with manufacturers.php

    empty your cache (in admin) this *might* fix it check your list of manufacturers (in admin) all look correct? turn off the manufacturers box if all else fails And, think about uprating to Phoenix, as your version is ancient. It was EOL a decade ago...
  19. burt

    Error with manufacturers.php

    It might be a very good idea to provide this: so what is the code on line 38 exactly.
  20. I believe it would be beneficial to save the RMA request in the Database so that both you and customer can track the status etc. Much like how an order is kept track of. What you have made is the "acorn" of a good idea that someone should run with.
  21. burt

    Nav Bar (Phoenix)

    If that shortcut works for you, great. For anyone else reading this in the future, please *attempt* (ie, have a go at building a simple module) do it the right way.
  22. burt

    [Contribution] Ship In Cart

    That "someone" would be YOU. If actual coding is too complicated for you, then you get it done by a competent coder and release it as an update. Don't rely on someone else all the time - be proactive yourself.
  23. Reminder that "Frozen" goes EOL on 17 May 2020, just 3 weeks away. I hope you all used the Sunset period of "Frozen" wisely.
  24. Reminder that "Frozen" goes EOL on 17 May 2020 [extended by request]. Now is the time to consider transferring to Phoenix, as you have 6 months before life support for Frozen is turned off.