Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 10/30/2019 in all areas

  1. 6 points
    BrockleyJohn

    Paypal Standard Payments Failing

    Thanks Martin, that fixed it for my customer's site. @saxcbr @Cary @cdetdi @Mac Fly please try copying the above file into your shops. You can then try resending an IPN from your Paypal account (finding it is tortuous): log in to PP, hit cog > Account settings scroll down to website payments on left menu choose Update next to Instant Payment Notifications in the middle of the first line of text, hit the link IPN History page This shows you a list of IPNs, defaulting to the last 24 hours - change the period if necessary and select one to resend [fingers crossed]
  2. 5 points
    Dear Mark, ( @mfleeson ) Based on the OSC, many branches were created. For instance: ZEN Cart, oscMAX, Solomono, WamShop and many other e-commerce applications. OSC was an open and understandable textbook for many coders who, having learned how to work with OSC, later created their own codes based on OSC. All of them have turned into independent products and are developing independently. I greatly respect Burt for his support for the OsCommers. He does everything perfectly. Phoenix - is it the development and continuation of the OsCommers? I think yes. Therefore, the OsCommers tradition must be maintained. No need to divide the community into groups. No need to do confrontation and conflict. We were a democratic community and must remain so.
  3. 5 points
    I think your missing the whole point of osC! osCommerce is released under the BSD licence and is open source so basicly is, Free redistribution of the software. The source code should be publicly available. The software can be modified and distributed in a different format from the original software. The software should not discriminate against persons or groups. The software should not restrict the usage of other software. If you care to you can read the full details here https://en.wikipedia.org/wiki/BSD_licenses As far as I know this has not changed... So yes jump in and get to know the code.....
  4. 4 points
    Hi all!! The idea of this post is to make it easier for new users who want to migrate to Phoenix 1.0.4.0, a list of addons available for free in the market, so that users can evaluate whether it is convenient for them to make a migration to Phoenix or continue in Frozen (which is stable and already has all the addons that an average user needs). I will list all the TESTED (by me) addons that are available. You can all publish the addons that you tried and are available in the market. Its prohibited : - Request support (for this you must go to the creator of the addon or the corresponding support page) - Mention addons that are not in the market The format for posting would be: Addon Name Link in the market Phoenix version that is certified to work Brief description of what that addon does Remember that the spirit of OSC is to share. love and peace Valqui
  5. 4 points
    v1.0.7.4 is tagged and announced; https://www.oscommerce.com/Us&News=166
  6. 4 points
    Agree 100% just dont have the time to keep updating every add-on every time the core changes. You just have to pick a point in time when its worth moving up but untill then it's simply best to state what version the add-on has actualy been tested on. In many cases the add-on may well work fine on a newer version of phoinex but unless the add-on has actaly been tested on it you can not claim this... Add to this that the number of people using Phoinex is low.... and among this small group the number moving to the latest version every time is but a hand full.....and the number using it for a live site?? unknown if any..... The need to rush and update add-ons to the latest release is not a big pull. So I would think those doing it out side the club will just do what they can when they can. I personaly simply pick a point in time to update to ( curently 1.0.4.0) and test my (very simple) add-ons to that version. Then when I update my test sites to a new version I check which still works and any new add-ons are then done to the new version. As and when a existing add-on is raised as an issue it is added to a list for update as and when time allows.
  7. 4 points
    mhsuffolk

    Paypal Standard Payments Failing

    paypal.com.crt
  8. 4 points
    A new version has been uploaded with these changes: Added gtin as an identifier. Added code for Phoenix compatibility. Installation just requires the files to be uploaded for Phoenix. Changed count code to pass php 7.3. Found by member @yahalimu. Changed default http to https in the googlefeeder file. Removed the code to check if mysql is being used. Mysqli is now required.
  9. 4 points
    raiwa

    Featured Products BS

    Uploaded Update: Featured Products CE v2.1.0 Featured Products CE v2.1.0. (CE Phoenix) Compatibility: Phoenix 1.0.4.x Lower versions, please use Featured Products CE v2.0.0. You may use the store side files of this version Featured Products CE v2.1.0. for Phoenix 1.0.2.x-1.0.3.x stores. Changes version 2.1.0.: Updated for OSCOM CE Phoenix 1.0.4.x Updated index content module template files to match Phoenix 1.0.2.x-1.0.4.x product modules Removed word length settings Bootstrapped Admin/featured.php and Admin/select_featured.php Removed Catalan and French admin language files Translated Spanish and German admin/select_featured.php language files Added Spanish and German store language files Updated instructions
  10. 4 points
    asro2004

    Stripe v3 module for SCA

    I've updated the module to version 1.0.13 to remove a potential SQL injection and tidy the account saved cards display when there are multiple cards (thanks @Smoky Barnable). @mhsuffolk I'm afraid the current version does not support Apple Pay, etc but looking at the Stripe documentation, it does not look too difficult to add. It just involves adding an extra HTML element to host a 'Payment Request' button which is displayed for certain compatible browsers, and some javascript and server code to support the creation and processing of a 'PaymentRequest' in a similar fashion to the handling of the 'PaymentIntent' in the current version. I'll add it to my list of things to do.
  11. 4 points
    Jack_mcs

    HoneyPot Captcha

    A new version has been uploaded with these changes: Added a page in admin to find and delete suspected fake accounts. Original code supplied by @Chadduck . Added a page in admin to allow deleting an array from the tracking table and to view the log. Added an option to verify the submitted IP. Added an option to verify the postal code. Added an option to verify the state and country pair is valid. Added an option to check the time to submit a form. Added filesize to dislay of the cron job results. Changed the option for the Math Captcha to use an image or text. Changed the captcha.php file to include a missing parameter. Found by @puggybelle Changed the mysql command to work for non-standard database names. Found by @Chadduck. Changed the cron output to show the size of the file. Changed the IP List setting to include check TOR IP's. Changed the names used in the hidden fields in case hacker scripts scan for the common name of honeypot. Corrected a typo in the error messages. Found by @puggybelle. Corrected the session name in captcha.php. Found by @ecartz. Fixed problem with the cpatcha code so it now works correctly. Removed a line of test code that was overlooked. Removed the notification option. All emails are now sent using the log tracker option.
  12. 4 points
    raiwa

    List of my Phoenix compatible Addons

    Uploaded updated Store Mode: Store Mode Phoenix 1.3.1. Changes 1.3.1: - fixed typo in header module english language file. Thanks to @mhsuffolk - fixed undefined error message. Thanks to @mhsuffolk Changes 1.3.0: - header module updated for Phoenix BS 4 - Updated header module message to show correct offline time if 2h auto setting is used - Updated admin header module message for 2h auto setting
  13. 4 points
    raiwa

    AJAX Attribute Manager support

    Uploaded new package : AJAX Attribute Manager Phoenix with; v 3.0.0 for Phoenix 1.0.0.0-1.0.2.x (older BS version support removed) v3.1.0 for Phoenix 1.0.3.x changes: + Updated for Phoenix 1.0.3.x compatibility + hooked all modifications + no core file modifications at all + removed modified files and references for older BS version
  14. 4 points
    burt

    Terms of Use.

    There is absolutely no problem with discussions about other carts, so long as the discussion is in the context of us here at osCommerce. For example, there would be absolutely no problem in someone asking; At the moment I am using "whatever-cart", I'm thinking about changing to osc...does osc have XYZ feature? And no problem in someone replying; It doesn't have XYZ, but if you install osc and then download this addon...you will then have something very like XYZ There is a problem in that person given advice such as; Keep using "whatever-cart" It's a matter of common sense. Does the reply that is being made "help the situation" with regards to osC gaining positivity. If yes: post it. If no: dont post it.
  15. 3 points
    Jack_mcs

    Upgrading to the latest version

    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.
  16. 3 points
    raiwa

    Wholesale (SPPC lite)

    Uploaded update: Wholesale (SPPC lite) 4.1.1. Changes: Update for Phoenix 1.0.5.0, - Fixed missing code in admin/categories.php hook for new products action. - Moved shopping cart class mod to shopping cart class override - Updated all boxes and content modules to match Phoenix 1.0.5.0 standard Compatibility: Phoenix 1.0.5.0. PHP 7.0-7.3 ------------------------------------------------------------------------------------------------------------- Older Phoenix 1.0.3.0 - 1.0.4.x versions please use Wholesale (SPPC lite) 4.1.0. Older Phoenix 1.0.1.0 - 1.0.2.x versions please use Wholesale (SPPC lite) 4.0.1. Older 2.3.4.(1.) responsive BS versions please use Wholesale (SPPC Lite) 3.0.4 Older 2.3.4.(1.) versions please use Wholesale (SPPC Lite) 2.0 -------------------------------------------------------------------------------------------------------------------------------
  17. 3 points
    valquiria23

    Phoenix - Russian Language Pack

    Спасибо Fredi @Fredi за поддержку oscommerce !!!
  18. 3 points
    JcMagpie

    Moving to Phoenix

    If only this was true! Unfortunatly the world of e commerce has moved on and most popular software offer the user a feture rich user experiance out of the box and not after hunting high and low for add-ons. Most new users will install and be very disappointed with what they see. They get no list of available add-on and will have to go looking for them and may or may not find them. I think most users will not even bother to look and just move onto another e cart that offers more out of the box. Have said this many times, keeping the core lean has nothing to do with removing fetures or not offering them at all. An add-on is of no use if no one knows it exists. A few users may go looking and find a few muscles be they legs or arms 😊 but many will just see a poorly dressed bag of bones and just look elsewhere. I could be wrong ( I hope I am) but only time will tell who is right.
  19. 3 points
    Jack_mcs

    Header Tags SEO

    A new version has been uploaded with these changes: Added missing code to display the manufacturer images. Changed pseudo module so it works properly with other addons. Changed code for the social icons page in admin to account for a deleted definition in CE. Found by member @mk_osc. Changed the open_graph code so it passes Facebooks test. Found by member @mk_osc. Changed fill tags code to correct php 7.3 errors. Found by member @Fredi. Corrected instructions for admin and added a missing php delimiter. Found by member @tobybailey. Corrected the path to the include file in admin since it would fail under some conditions. Corrected coding mistake in admin functions file. Found by member @241. Fixed Copy To code for products in admin. Found by member @lucsangel.. Fixed spelling mistake in the admin/header_tags_seo_keywords.php file. Found by member @mk_osc. Fixed code mistake in admin/manufacturers.php that precented the manufacturer description from being saved. Increased the limit for the meta description tag to 300. Google made this change in December, 2017. Moved the category and manufacturers descriptions code to modules (CE or late 2.3.4 version only). Removed unnecessary code from index.php. Removed unnecessary code from modules/header_tags_opengraph.php for OG availability. Found my member @BrockleyJohn. Removed code from admin so View Result is not forced to an http connection. Removed Googles +1 option and code. Removed remaining TABLE_ definitions (CE only). Removed all pre-Frozen files. Please note that this version focuses on changes for Phoenix. I have tested it and did not find any problems but that is in a controlled environment so I strongly suggest that you try the installation in a test shop first. In the lease, make a complete copy of your shops files in case you need to restore. Also, there are some core-changes needed. There's no way to avoid those since this addon uses the same sections of code as the default, in several cases. For Phoenix, the instructions should be correct. For Frozen, they may not be. If this addon is already installed, you can skip the category and manufacturer file changes in admin. The changes for the categories file have been reduced for easier installation but the resulting code is the same as before. For pre-Frozen shops, the addon will still work fine with them. But given my time is very limited, I have to stop offering free support for those versions.
  20. 3 points
    ecartz

    Use Search-Engine Safe URLs

    False. Once upon a time, search engines paid attention to things that were in the domain and path but not query parameters. So it made sense to put things like product ID in the path rather than query parameters. But all major search engines (Google, Bing, Yahoo, etc.) can handle query parameters now. It was never quite right anyway and is totally useless now. It just makes it look like you have duplicate pages. The only reason it's still in core is that I haven't deleted it yet. Maybe next month. If you really want better URLs, then install something like Ultimate SEO URLs or similar. That's not quite right. It takes the = signs out too. https://www.myshop.com/product_info.php/sort/4d/cPath/22/products_id/829 What it should do is make it look like https://www.example.com/product_info.php/products_id/829?sort=4d&cPath=22 but it's really an inferior solution. Better to use an SEO URLs contribution so you can get the keyword benefits. E.g. https://www.example.com/stamps.html?sort=4d&cPath=22 Note that Amazon.com does this like https://www.example.com/1989-German-first-class-stamp/dp/[product_id]?what=ever and then just ignores the first thing after the domain. But they only do that for new products. For old products, they leave the https://www.amazon.com/exec/obidos URLs even though Obidos has been turned off for more than ten years. Anyway, when I delete SEF URLs, I plan to make it easier for people to make their own URL Apps. Ideally I'd like to upload SEF URLs as an App in the marketplace.
  21. 3 points
    TomB01

    UPS XML 1.7 for Phoenix

    Well, I have it working! It wasn't your post specifics, but the idea you hit upon in the SQL inserts above. I kept looking at the error codes e-mails that were stating "Missing/Illegal Shipper/Country Code" trying to figure out which was the issue - Shipper or Country Code. I decided to create log files on the server. Then I compared the Phoenix log file to my working 2.3.4 log file. The UPS reply on the working log file was lengthy. Then I went to WinMerge to compare the two log files exactly. The 2.3.4 log file had CountryCode "US", the Phoenix log file had CountryCode "United States." Long story short, my Chrome browser was auto-filling the Admin settings for UPS XML shipping and I accepted "United States" instead of following the instructions that stated Enter the country's two-character code. What a dummy I am! Checked it again, then the error code changed to "Invalid Destination." I guessed the UPS Server was very smart, so I input my own real address. It worked. Bottom line, the insert into the languages file suggested by Burt fixed the Admin errors about the "UPS_SERVICE_CODE_." Elsewhere, I had to input into the upsxml.php file, complete path strings instead of the DIR_ stuff, and remove the TABLE_ prefixes and use lowercase database table names. Then I ensured that correct data was entered into the Admin settings, and used a REAL checkout address. Success! Attached are the modified-for-Phoenix includes/modules/shipping/upsxml.php and includes/languages/english/modules/shipping/upsxml.php files. (Enter your own store's path string where needed.) upsxml.php upsxml.php
  22. 3 points
    Well meant advice; You have multiple hook files performing the catcha routine ... this can be done from one hook file. Take a look at the core bootstrap example where it is placing "stuff" in two different locations; https://github.com/gburton/CE-Phoenix/blob/master/includes/hooks/shop/siteWide/bootStrap.php#L23 & https://github.com/gburton/CE-Phoenix/blob/master/includes/hooks/shop/siteWide/bootStrap.php#L30 Having just one File with all the hooks (for a given "XYZ" [in this case captcha]) in it, is; simpler for you in terms of support simpler for user in terms of having to upload/delete etc let us say that the user wanted to not use your captcha anymore, and deleted the file that displays the form...the other files gets missed somehow...they have a broken site. Not good for them [loss of potential sales], not good for you [support issues], etc etc Hooks are a big part of Phoenix' future, so well done on being one of the pioneers of them.
  23. 3 points
    raiwa

    Display Tax Info V3.0

    Uploaded Update for Phoenix flagged for Phoenix: Display Tax Info Phoenix Changelog Version 4.0 - updated for Phoenix 1.0.3.x - moved currencies_mod class extension into siteWide hook. This allows to use it also for modularized shopping cart and other modularized pages with content module call in data section of the page.
  24. 3 points
    raiwa

    List of my Phoenix compatible Addons

    Uploaded: Points and Rewards Phoenix
  25. 3 points
    JcMagpie

    New themes for Phoenix

    So not everyone is happy to edit files in order to make changes ( “You can please some of the people all of the time, you can please all of the people some of the time, but you can’t please all of the people all of the time”) Not a problem just use this header_tag add-on and you can select the required theme in admin. It's about as simple as i can make it. Any other changes are down to the user. Remember you have 18 themes to select and each can be chnaged further using the color tweak add-on here JcM Color Tweak V1.1 so you have millions options to use on your site! Has been tested on Phoenix 1.0.2.2 only. Enjoy! JcM New Themes Header Tags-V1.0.zip
×