Jump to content

TomB01

Members
  • Content count

    403
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by TomB01

  1. TomB01

    NEW! Complete Order Editing Tool!

    @BrockleyJohn, A setting somewhere in the code perhaps? I didn't see anything in the Admin Configuration->OrderEditor. (Doesn't mean I didn't miss it, though.)
  2. TomB01

    NEW! Complete Order Editing Tool!

    I have what I hope is a simple and quick question. I installed the latest order editor at the time and have since stopped at Phoenix 1.0.5.0 on my active store. The Order Editor from BrockleyJohn was v1.2.8. Anyway, is there a way for Orders to display without going to edit mode directly? I click on Edit from the Orders list in Admin, but then it goes directly into the Order Editor, instead of the Details view. Once in the Order Editor, I have a "Details" button that I can click to get out of the Order Editor and update the status. Is there a way I can fix it so that it goes to the Details view from the Admin Orders list? When it goes directly to the Order Editor, it runs through my shipping modules and is wasting a lot of time. It's not too often that I have to edit an order, thankfully. So, being able to click directly to the Details view would be very helpful.
  3. FYI - It seems that every time I edit/add a Featured Product in Phoenix 1.0.5.0, it requires another Admin login and form re-submission. Is this normal? I haven't noticed it with any other Admin tool.
  4. I started with r1.8 and the last time I looked, I could not find it on the Apps Marketplace. Hmm … guess it was my search error, because it's there, now. Anyway, those files in my post a page back should work if you start with the r1.8 version, uploaded by kymation as you say - 2 years ago. Do this to the database: Then do the stuff in this post: It should work. I've had to re-edit the modules.php file with every update of Phoenix, but my USPS shipping has been working all the way through from 1.0.4.0 to 1.0.5.0. I've posted this before for you, so if it doesn't work, I apologize. There may be something else with your store that's different that we're not taking into account.
  5. That fixed it in both installs! Thanks! Glad to know it wasn't something I had messed up again. 😉
  6. Question - I've loaded this on a Phoenix sandbox test store and on my proposed Phoenix primary store (both updated to 1.0.5.0). This happens on both installs: clicking on the "See More" button re-orders the featured products, while removing the images. My sandbox install is using my existing 2.3.4 store's images, etc. However, my proposed primary Phoenix store is still using the default apples, lemons, tomatoes, etc. I haven't touched the images folder. The error is consistent between both. The img src tag seems to be stuck on img src="images/" in the featured_products.php file. The index.php file retains the full link to the image, but not in the featured_products.php file (it only shows the Alt Text, not the image).
  7. Turns out, I needed this, too: ALTER TABLE `products` ADD `products_gtin` CHAR(14) NULL AFTER `products_ordered`; I just hadn't gone far enough in my testing. This is an additional field that was added in Phoenix (or sometime after 2.3.4), but is ordered before two other fields in the structure list. Thus, the "AFTER 'products_ordered'.
  8. Many thanks for this add-on! I was a bit tired of seeing trivial things in my store default to the main page, just because they've been added last. Something like a Featured Products was sorely needed. For the dummies like me, though, please let me suggest some changes in the Install_manual.txt: Change this - to this - Step 3: - Edit the Header Tags Module, "Table Row Click jQuery," by ticking the "featured_products.php" Pages checkbox. - Make sure you install at least one of the following modules: under Modules-Content, "Featured Products" (index), "Featured Products" (index_nested), or under Modules-Boxes, "Featured Products." Once installed, you can activate or deactivate them.
  9. So, Select "p.field1, p.field2. pd.field1, pdfield2 from tablename1 p, tablename2 pd;" is using an arbitrary character(s) to distinguish between different tables in the same Select statement? I guess ArtcoInc is showing that, too, the way he expanded the SQL statement. Cool!
  10. Dan is correct and glad you found the solution. To others - if this will help - take a look at that error message that Krisz1 got: I'm sure this is like explaining 2+2 to some of you, but when I saw similar messages, I keyed on the "Unknown column" part. That tells you there's a field (column) missing in the database table the follow-on SQL statement is trying to access. Then I looked in the SQL "Select" statement for the "from" word. The name that comes after the "from" word in the SQL statement is the database table. You will also see the "products_gtin" field name in the collection of field names that the "Select" statement is trying to gather. So in this case, "products p" looks like the source table for the SQL statement. I don't know enough about SQL to know if the comma after that is specifying another table. I also don't know what the "p" means at the end of "products," or at the beginning of the field (column) and table names, but that doesn't matter. I'm going to check the "products" table, first. With those partial bits of information, go to the phpAdmin (or whatever client you're using) and find the "products" table in the database. Look at the structure for the "products" table in 2.3.4 and then look at the structure for the "products" table in Phoenix. In phpAdmin, there's an actual tab for "Structure." That should show you the extra fields (columns) existing in 2.3.4 that you need to add to Phoenix. You should see the "products_gtin" field in the 2.3.4 "products" table (in this example). Develop a similar SQL "Alter" statement as above, adjusting/editing for the variable type (TEXT, VARCHAR(##), etc.). Run that in the SQL window in phpAdmin on the database (don't touch the 2.3.4 one), then re-load the Phoenix store page that caused the error. It should go away. Or, at least the error changes to something else that you can also research similarly. Eventually, you should arrive at no errors when you re-load the store's page in question. Interestingly, I don't have a "products_gtin" field in my "products" table - either 2.3.4 or Phoenix. That's probably because I never installed the same add-ons that you guys did. So, maybe everyone arguing against a do-all script is correct. I had a horrible experience in the past trying to use an all-at-once SQL script for porting an OsC database (coming from MS2.2 to 2.3.4). Granted, it's not a single button-push, but maybe it really is better to encourage the logic and method of manually copying the database. Remember to back up, back up, back up - both before and after. 😉 This is very rudimentary, but hope it helps ...
  11. @burt, Ha! Right on cue: you just dropped another supporters code down the chimney! 😉
  12. Yes - no disrespect meant toward Gary. It's sort of like Santa Claus keeps pushing presents down the chimney, but you're still trying to unwrap the first one. 😀
  13. OK - did that and promptly got error messages in the Admin and fatal errors in the Store. I've been working on this, off and on, since Thanksgiving - including about two solid weeks when I was on vacation during Christmas/New Year's. If I had tried this a month or so ago, I probably would've had a heart attack. However, I've blown it up so much since then, that things are not phasing me so much anymore. Using the sandbox helps immensely, though. So ... the phpAdmin indicated a successful copy of all the tables - excepting the configuration, configuration_group, sessions, and whos_online were not copied. (Copy was done with phpAdmin as mentioned earlier in this thread.) Starting with the Phoenix Admin, it blew up on the Supporters Low Stock Alert and when accessing the Catalog->Categories/Products, not recognizing a couple of fields in the products table. I researched that by comparing to another Phoenix database and discovered that products_cost and products_reorder_level had to be added. In this case, I was able to reference the Readme files for the supporters' code (d18 and d20, to be exact) and run the SQL statements again (ALTER TABLE products ADD etc., etc.). Checking the store, it blew up with error messages on the categories_description and products_description tables. Turns out, Phoenix added four fields to the categories_description table and three fields to the products_description table. Copying the Alter statement from above, I ended up with the following that I ran on the database: I'm not sure this was documented anywhere. At least, I haven't seen it while following the Phoenix threads since T-giving. I'm coming from 2.3.4, so maybe these fields were in CE Gold or Edge? Final step was to upload all my existing catalog images and it now appears my sandbox is a working version of my store in Phoenix, with all the supporters add-ons. 🙂 I will keep testing it for a couple of days and try porting everything over to my actual store this weekend. I sort of hope Gary doesn't have another update between now and then. 😉
  14. More likely to break it, than slim it down - if I do that.
  15. Excuse me for going back to the well again, but Got SQL? (to list the settings of the tables) In particular, can you confirm the settings that are important for Phoenix? Is anyone working on a migrate-to-Phoenix-from-older-OsC Checklist? That might be a small effort for potentially great reward. I have these databases backed up six ways to Sunday, multiple copies of the databases, and an operating sandbox. So I can mess with parts without breaking anything, but it still seems daunting.
  16. Well, seems like I got a pretty comprehensive result when I used a wildcard for "id." As in: Unfortunately, the magnitude of the response to that is leading me to believe that this is close to impossible. Looks like moving the entire database is the better option. I'm just concerned because when trying that in the past, I ended up with entirely different configurations than the default Phoenix.
  17. @ecartz, This is great info - thanks! Any clue on how to find out other fields that are shared among tables? EDIT: Never mind - it's further down in your stackoverflow link - very helpful!
  18. This looks like a great strategy, but I'm having trouble finding relations between tables. Isn't the table address_book an important part of migrating customer accounts? How do I find these relations if I'm wishing to port data manually, only as few tables as needed?
  19. TomB01

    UPS XML 1.7 for Phoenix

    NOTE: I had to use the above to get rid of an error in the Admin after updating to Phoenix 1.0.4.2: : constant(): Couldn't find constant UPS_SERVICE_CODE_Array in/home1/xxxx/public_html/xxxx/catalog/includes/modules/shipping/upsxml.phpon line1146 Using ecartz' code replacement suggestion above in the includes/modules/shipping/upsxml.php file fixed this error in the Phoenix 1.0.4.2 Admin. My other legacy modules FedEx Web Services and USPS Rate V4 were unaffected (still required the modded modules.php in Admin, however).
  20. TomB01

    UPS XML 1.7 for Phoenix

    Trying to get this to work with Phoenix 1.0.4.0. I edited the upsxml.php file to use 'includes/classes/' instead of DIR_WS_CLASSES. So, I was able to install and enter all of the appropriate info. I get two errors, one not so bad, I think, but the other blows up the checkout. In Admin, I get the following, but it appears to have saved all the values I entered anyway: Warning: constant(): Couldn't find constant UPS_SERVICE_CODE_--none-- in /home1/xxxx/public_html/xxxx/catalog/includes/modules/shipping/upsxml.php on line 1128 In the checkout, it blows up with this: 1146 - Table 'my-database.TABLE_ZONES' doesn't exist select zone_code from TABLE_ZONES where zone_name = 'Tennessee' and zone_country_id = '223' and length(zone_code) > 0 [TEP STOP] The Zones table definitely exists and the Zone_code for Tennessee shows "56." (I also tried UPS Choice and I think there's no chance with that. Besides, I prefer one that uses a UPS account.)
  21. TomB01

    Google reCAPTCHA v3

    OK - I'll continue work on it. 1. The Google Admin Console is buried worse than most things I've seen. Maybe I'm mentally challenged this weekend, but the only way I got to it was a through a Google search to this page: https://developers.google.com/recaptcha/docs/v3. Even then, a link was buried in the text about halfway down. I could not find it anywhere in my Google account settings or in the other reCaptcha documentation, particularly not in the Admin Console documentation itself. I probably kept overlooking it in the page above, but who knew? 2. Apparently, my keys are only valid for reCaptcha v2, since I had already registered for Gary's Phoenix add-on. The reCaptcha keys also appear to be tied to my Google account, since the reCaptcha pages direct one to "choose" which you want. I suppose I will need to create another Google account if I want to use more than one type of captcha, e.g. reCaptcha v3 for my 2.3.4 site and reCaptcha v2 for Phoenix. Note that these are Google complaints only - not for this add-on! Anyway, thanks for the help - it is much appreciated.
  22. TomB01

    Google reCAPTCHA v3

    I'm confused. If it doesn't appear, how do I know it's doing anything at all? The reCaptcha in Phoenix shows the Google "I'm not a robot" checkbox, then proceeds to give you visual test. I'm trying to stop all of these Russian user accounts and Contact e-mails that keep spamming my 2.3.4 store, until I have Phoenix ready. It's taking a lot of my time to clean this junk out when I could be doing more work upgrading to Phoenix. I had 20 spurious accounts I had to remove just this morning! Can I just manually add the Google reCaptcha code to my 2.3.4 contact_us.php and create_account.php pages?
  23. TomB01

    Google reCAPTCHA v3

    Anyway to make this work under php 5.4? I tried replacing "[]" with "array()" everywhere, but the google recaptcha doesn't appear on either page, create_account or contact_us.
  24. TomB01

    UPS XML 1.7 for Phoenix

    I think many of you know that the OsCommerce Apps Marketplace is a mess. I'm not trying to be overly-critical, just to confirm that you shouldn't depend on it to find the latest updates, documentation, etc. Going right through the Apps Marketplace and searching for "UPS," you will never find the download that I started from. This is the link that I believe represents the latest UPSXML add-in: https://apps.oscommerce.com/z6l1O&upsxml-version-1-5-for-oscommerce-2-3-x Notice that the link string says, "version-1-5." You'll find that when you open the zip file, the top-level folder says, "UPSXML_v1_7." Further, opening the "UPSXML install.txt" file uses the heading, "UPS XML Rates v1.6.1 for osCommerce 2.3.4 2017-04-11" So, in three steps with the same download, we go from Version 1.5 to Version 1.7 to Version 1.6.1. This add-on was not found from the Apps Marketplace menu or search itself, instead, it came from a Google search. 😖 Anyway, the UPSXML that I have working in Phoenix 1.0.4.0 is based on the download referenced from the link described above. I am preparing to update to 1.0.4.1 and 1.0.4.2 and wanted to make certain I had everything documented in my files. I discovered that my folder for the UPSXML add-on was "UPSXML_v1_7" and could not find where the heck I got it! I will try to upload this as a new revision to the Marketplace, if I can. However, I'm going to try to go through the greasemonkey and ecartz hook mod just above, first.
  25. TomB01

    Google reCAPTCHA v3

    Never mind - my mistake. Thanks for the add-on!
×