cigarsforless

sadly it seems that all the apps made over decades in support of the original versions of osCommerce are no longer available online via this site. while I understand the new owners want to move forward, tossing out access to all the legacy addons is nonproductive in my humble opinion. At least the forum is still here (for now?)

YAY! that worked, I owe you a beer for sure

was scratching my head trying to figure out why domestic rates are failing but international are still working thanks so much! changed the TM to RM in the usps.php file but still no domestic rates, sigh, I really hate the post office devs

nope, tried to change just the 80 to 443 and no results at all are returned 😪

looking in includes\classes\http_client.php I find this /** * httpClient constructor * Note: when host and port are defined, the connection is immediate * @seeAlso connect **/ function httpClient($host = '', $port = '') { if (tep_not_null($host)) { $this->connect($host, $port); } } /** so perhaps it is as easy as just changing the 80 to 443 in the code from my post above?

I too have the same issue as OldPete in need up updating to https but my code has been modified for Multivendor Shipping (MVS) This is the block I need to change $http = new httpClient(); if ($http->Connect('production.shippingapis.com', 80)) { $http->addHeader('Host', 'production.shippingapis.com'); $http->addHeader('User-Agent', 'osCommerce'); $http->addHeader('Connection', 'Close'); if ($http->Get('/shippingapi.dll?' . $request)) { $response = http_chunked_decode( $http->getBody() ); } $http->Disconnect(); is it just a matter of changing all references to http with http nd 80 to 443?

looks awesome and can't wait for Phoenix update, please PM when available to purchase the pro version for Phoenix

old stock version of search engine safe urls set to true? that should be off as it never worked and was ancient to see if you have that as a holdover from previous versions of Phoenix open phpmyadmin and search for SEARCH_ENGINE_FRIENDLY_URLS in the configuration table (in configuration_key) that was removed from Phoenix in 1.0.5.3 but may still be there if you missed an update step if it is there, set to false in configuration_value this part of the code you commented out is only activated when $search_engine_safe = true and that is set by the above (now removed) configuration key SEARCH_ENGINE_FRIENDLY_URLS set to true

yep, just edited includes/functions/href_link.php with the changed function and all is good

@Jack_mcs just noticed that html_output.php was updated in 1.0.7.4 so that overwrote the change made on initial install the function to replace that was in includes/functions/html_output.php it is now located in includes/functions/href_link.php is is just a matter of modifying the The HTML href link wrapper function in that file?

just upgraded to Phoenix 1.0.7.5 and Ultimate SEO URLs now seems to be broken, old rewritten urls work, but none of the site now produce the nice friendly urls is an update to this must have addon in the works?

lol, am blind without enough coffee in the mornings

still on 1.7.3, best get on to 1.7.5 I guess

previous version 3.3 required changes to catalog/includes/functions/html_output.php new version states no core changes shop side, do we revert the core changes back to the original? I do not see that file in the package so not sure if it needs to stay with the core change from 3.3 or not

perhaps I am blind but while I see the change log info I can not find any update instructions in the install documentation, have previous version installed in Phoenix 1.7.3

anybody have this (or something similar) working in Phoenix?

does anyone have MVS working on Phoenix? I have Dimitri's updated version working on Frozen, mvs-for-v2-3-4-bs-edge but wondering if there is anyone out there who has it installed on CE Phoenix With the desire of "no core changes" in Phoenix, I wonder if this is doable. Is anyone familiar enough with MVS willing to take on paid work to update this essential add-on to work with CE Phoenix?

agree on both parts, woo would have cost me a small fortune just to get to the point where i could actually determine if it would do the job correctly as suits my business needs, turned out i would have to buy so many modules just to test it out that I gave up that route. As far as osc having a free version of add-ons and paid for full featured ones, I think that would be a great idea to help fund the project get the bells for free but pay for the whistles

simple to install, but over complicated in some aspects and be prepared to pay thru the nose for each and every must have add on, basics like ups shipping will set you back 79 bucks if you want live rates, same for usps, fed ex the list goes on and on. much rather support osc and tweak some code myself than pay a grand or 2 a year to woocommerce

looked at and tried out WooCommerce and CS-Cart and a few other systems as an alternative to upgrading my 10 year old 2.2-MS2 site. wasted time and money on both, sure they have lots of users but BOY are they much more complicated to use and configure and still lack a lot of what osc has. long story short, back to plugging away at installing (and trying to find current versions) of all the add-ons I have in the old site to get the new version up and running. If I could suggest 1 thing only to improve osCommerce it would be to fix the market place. search is next to useless, you are better off using google to bring you to the addon page you want. limit results to 2.3 version and you still get tons of apps that are 8+ years old and do not work with edge-frozen-phoenix without major updating but diligent searching will eventually bring to a new version in most cases 1 other thought, documentation for creating addons? to be honest the new modular system is an extensive learning curve for those of us who are oscommerce users from way back but not very proficient coders. current documentation is based on ancient code using phh 5???

the sitemap uses 2 category tree classes, 1 with just categories, 1 with cats and products. as I have over 200 categories and 5k products it results in a massive page trying to get it so if user want to search for a product, they can click on the category to list products, but only show the ones they have opened, rather than a massive page that takes forever to scroll through

the jquery script supplies the toggle to show and hide the links <script type="text/javascript"> $(".hide-products").click(function() { $(this).find(".hidden-content").toggle(); }); </script> what I am having trouble with is where in the code to place the divs so they appear on only the categories. with the above js, no unique id is required, just need the following to appear at beginning of category link <div class="hidden-content"> and the closing </div> at the end of said category. something like this... <div class="hide-products"> Category 1 link here <div class="hidden-content"> <li>category 1 product 1 link</li> <li>category 1 product 2 link</li> <li>category 1 product 3 link</li> <li>category 1 product 4 link</li> </div> </div> the css is this .hidden-content { display: none; border: 1px solid black; }

thanks anyways, I'll keep at it and post here if I have any success

hi @Jack_mcs been playing around with the sitemap and trying to get the products to hide unless clicked by using jquery and css as per the example here http://jsfiddle.net/7Rqqd/ my main issue is getting the <div class="hidden-content">...........</div> to be placed only at beginning and end of each categories products. the goal is to hide all products unless the category link (or an arrow in front of it) is clicked and then the products are expanded for that category only I've been playing around with classes/category_tree_standard.php but can't quite seem to get it to work correctly thought maybe you could have a go at it as you know your code better than I can try and figure it out.

found the culprit in sitemap_seo.css @media (max-width: 640px) { div.sitemap { font-size:10px;} #sitemap-display-wrapper {flex-direction: column;} .site-map-contact {font-size:10px;} } font-size:10px; is the culprit!