altoid

@@jenodorf
 
Hello, here's how I'm doing that procedure.
 
The first image option is where I put a smaller scaled down size of the main product image. Maybe 200x200 with a lower resolution. It'll hopefully come in at 3-4 kb.
 
Then in the next "larger" image upload I put the same image but larger in scale, maybe 500x500 in a decent enough resolution to look good on the screen but not so much as to grow the file size. Hopefully around the 20-30 kb range.
 
Then every "larger" image thereafter, if I use it, is a as just above (500x500,etc, etc) of different product image pics that may be good to show.

After my service provider said they are migrating to 5.4 in january (from 5.2) i also got these errors and fixed them with the following
 
in admin/attributeManager/classes/amDB.class.php and in admin/attributeManager/classes/stopDirectAccess.class.php
 
every function needs to have public static placed in front of it eg
 

function authorise($sessionVar) { amSessionRegister($sessionVar); $GLOBALS[$sessionVar] = stopDirectAccess::makeSessionId(); }
 
becomes
 

public static function authorise($sessionVar) { amSessionRegister($sessionVar); $GLOBALS[$sessionVar] = stopDirectAccess::makeSessionId(); }
 
and finally in admin/attributeManager/includes/attributeManagerGeneralFunctions.inc.php
 
change
 

$attributeManager =& new attributeManagerAtomic(amGetSesssionVariable(AM_SESSION_VAR_NAME));
 
with
 

$attributeManager = new attributeManagerAtomic(amGetSesssionVariable(AM_SESSION_VAR_NAME));
 
 
and change
 

$attributeManager =& new attributeManagerInstant($_GET['products_id']);
 
with
 

$attributeManager = new attributeManagerInstant($_GET['products_id']);
 
This removed all warnings for me

Thanks for this fix @@Gergely
 
In my case I think this was only showing up when google was recrawling cached pages that no longer exist. These are soft 404 errors in webmaster tools.
 
My problem product pages are now going from an incorrect 200 status showing something like this:
 
Warning: Invalid argument supplied for foreach() in /home/myusername/public_html/includes/modules/ultimate_seo_urls5/page_modules/product_info.php on line 102
 
Catchable fatal error: Argument 1 passed to aPage_Modules::linkText() must be an array, null given, called in /home/myusername/public_html/includes/modules/ultimate_seo_urls5/page_modules/product_info.php on line 170 and defined in /home/myusername/public_html/includes/modules/ultimate_seo_urls5/abstracts/page_modules.php on line 338
 
To a correct 404 status page generated by FWR Media looking something like this:
 
Page not found
The page you were looking for could not be found. Please click the below link to return to My Shop Name
 
Posting this here so others with the same issue can see what occurs....

Temporary fix for 404 page handler after v2.3.3.2 updates
 
page_modules/product_info.php
 
(about in 98 line) change:

if ( false === $text_array ) {
 
to:

if ( is_Null($text_array) || false === $text_array ) {
 
 
I see that mySqli_query gives back different returns by queries so would be better to use v2.4 core database philosophy...
 
Example:

if (tep_db_num_rows() > 0) { than do something }
 
I hope @@FWR Media Robert asap will give right directions

*** WARNING *** This WILL be cross posted for clarification across ALL USPS shipping module threads.
 
There are, for all intent and purpose, TWO different modules, 2 very different modules. One of those modules has morphed itself 3 times in the ADD-ON section of osCommerce.com/info/xxxx
 
When posting to any USPS module thread PLEASE state which osC vX.X.X as well as which USPS module you are using. If you are unsure what version of the USPS module you are currently using, PLEASE paste the first few lines of /catalog/includes/modules/shipping/usps.php file here so maybe we can help you make the determination.
 
Here is my take on the module morphing:
http://addons.oscommerce.com/info/8327
USPS Rate V4 Intl Rate V2 - v.1.0
at some point was set to NOT allow uploads to the module, essentially closing it to further updates.
this morphed into:
http://addons.oscommerce.com/info/8403
USPS Rates ServerV4 (for osc2.2)
which also at some point was set to NOT allow uploads to the module, essentially closing it to further updates.
this then morphed into:
http://addons.oscommerce.com/info/8702
USPS Methods Rates V4 Intl Rates V2 - 01-27-13 Update
this one is being currently maintained, within thread http://www.oscommerce.com/forums/topic/383307-usps-rate-v4-intl-rate-v2-official-support-thread albeit with some errors still in regards to First Class rates and handling fees. See post #748 above for that: http://www.oscommerce.com/forums/topic/383307-usps-rate-v4-intl-rate-v2-official-support-thread/page__st__740#entry1678247
 
The second module is:
http://addons.oscommerce.com/info/487
USPS Methods
This one is being maintained within the ADD-ON section and within thread
http://www.oscommerce.com/forums/topic/146950-contribution-usps-methods/ HOWEVER there are MANY MANY updates there.. 5.2.x 6.x and now 5.3
 
There is at least one further active USPS module thread:
http://www.oscommerce.com/forums/topic/393466-heads-up-july-28-2013-usps-name-change-for-express-mail/
Heads Up: July 28, 2013 USPS Name Change for Express Mail
which is mostly referring to the USPS Methods module #487 with some cross posting going on there as well.
 
So there you have it.. please lets try and post to the proper thread and let everyone know what you are using so we can best help you!

It tested some shipping destinations to countries in the middle east. No problems with the code but now I have an NSA van parked outside my house. o:)

I'll test Jim, thanks for tackling this.
 
Before your post I was wondering if there was some way to get around having to manually modify the USPS module every time they make changes that changes that cause all this grief. But my limited coding skills won't cut it.
 
At least I can test....fire away.

It tested some shipping destinations to countries in the middle east. No problems with the code but now I have an NSA van parked outside my house. o:)

The current USPS shipping modules (USPS Methods, USPS Rate V4, Intl Rate V2, stock osCommerce 2.3x) all have a major problem -- they depend on the Service names that USPS supplies. Since USPS seems determined to change these names every six months or so, these modules break and must be patched twice a year. This should not happen, and it doesn't need to.
 
The quotes that USPS returns are keyed to a Service ID (called CLASSID.) These are (mostly*) unique numbers that never change, or only change when a service is deleted or added. These numbers are a much better way to select the service(s) desired, as the module will not break when USPS changes the service names.
 
If this system had been in use before the July changes, the only difference that anyone would have noticed would have been different service names showing up on the checkout page. No broken checkout, no thrashing to get a fix implemented, no lost sales.
 
I've done some preliminary testing, and I have a plan to fix this. I intend to use some of the code from the USPS Rate V4, Intl Rate V2 module since I like the way it is set up in the Admin. The rest of the code will be rewritten.
 
I have in mind an adaptive model that will require an extra step in the install process. The first edit of the module upon install will require a valid USPS Web Tools username. That will be used to send a dummy quote request to the USPS server for all available services, domestic and international. The response to that will be stored and presented in the second step as a list of services that may be selected. The selected values will then be stored in that step.
 
The installer will allow the selection of services by their current names. The names in the Admin will not change if USPS changes their API since those values are stored in the database. However, we are only comparing against the CLASSID, so the store side will continue to work and show the updated names.
 
Updating the names on the Admin side can be done by uninstalling/reinstalling the module, but that will normally not be necessary. You will only need to do that if USPS has added a new service that you want to offer to your customers or they have removed a service that you were offering. Doing an uninstall and reinstall is a lot simpler than modifying the code to make it work again.
 
*Yes, there's one problem with this approach -- the CLASSID for all First Class services is 0. That will have to be treated as a special case. That makes First Class more fragile, but USPS doesn't seem to change those services very often, so it's not likely to be a huge problem.
 
Any and all help with this is very welcome. I can use help with the code, of course, but feature suggestions and testing help are appreciated as well. Let's see what we can do with this.
 
Regards
Jim

I've started development on a revised USPS module that won't break every time USPS changes the services names. Anyone who is interested is welcome to visit this thread.
 
Regards
Jim

My husband, who is very knowledgable about PHP and posts here often, and I have spent countless hours since Sunday trying to fix this mess. We have never gotten the service names to show up (despite using the USPS naming nomenclature from their July 2013 web tools release document), have not gotten international or Standard Post to work at all, and can't get the handling charge to work. So, we set up 3 modules for zone rates, one for Standard Post, one for Priority Mail (both domestic and international in one module), and one for Express Mail (again, both domestic and international in one module). It took about an hour to define the prices by weight for each service/zone, but it's all loaded, working fine, each zone has our handling fee, and BEST OF ALL, we do not have to connect to the USPS for it to work! No matter what the USPS does in the future, our zone modules will be unaffected (although we will have to manually increase prices if there is a price increase, but is less than an hour's work and could be covered by upping the handling fee). I remember the USPS website was down for almost 2 weeks several years ago around the holidays, and then their January 2013 changes caused us problem for almost a week, and now this 6 months later.
 
Zone shipping works great and will NEVER be affected by a silly name change by the USPS or any other useless change they implement to make their services less user-friendly.

Jim....thank you for sharing your knowledge and expertise with us. :thumbsup:

@@kymation
 
Hi Jim,
 
Got a test install done using mega fish and jsu updated the superfish files with the latest from git hub
 
https://github.com/joeldbirch/superfish
 
Used the mega fish.css cause he has a nice turning arrow :P well tested on ipod touch and he is working good so will test on another mobile device later as far as i can see he is working straight out of the box link to demo also works good in the vertical mode like your accordian menu by changing .sf-vertical in the superfish css .
 
so all in all think it is ready for a few live tests will use it in a live site I am building in a few weeks.
 
As regards the theme colours I personally think let superfish handle the css I think design wise it becomes a bit overpowering if there are a lot of categories IE: Accordion menu using the theme easy to make blend in so see no problem there.
 
The cache is important remember from the old superfish menu in ms2 that he generated a lot of queries.
 
Thanks for the file have been fiddling with this for months and just could not get to work.
 
Regards
Joli

How to add Woothemes flex slider as a front page module
 
Please note only the essential switches are included as parameters in the module, if you want anything fancy you'll have to extend it, or modify the javascript directly in the code
 
1) Javascript
 
Download the last version from
http://www.woothemes.com/flexslider/
 
You need to create a new folder as /ext/modules/front_page/flexslider/ and put the css file and the javascript file in this folder (following the front_page convention for external files).
 
2) Language files
 
for each of the languages you use, create a flex_slider.php file as
catalog/includes/(language)/includes/modules/front_page/flex_slider.php
with the following content:

<?php /* $Id: flex_slider.php v1.0 20101109 Kymation $ osCommerce, Open Source E-Commerce Solutions http://www.oscommerce.com Copyright (c) 2010 osCommerce Released under the GNU General Public License */ define( 'MODULE_FRONT_PAGE_FLEX_SLIDER_TITLE', 'Flex Slider' ); define( 'MODULE_FRONT_PAGE_FLEX_SLIDER_DESCRIPTION', 'Control the function of the flex slider module on the front page.' ); ?>
 
3) ftp flex_slider front_page module flex_slider.php
 
Load up the attached php as catalog/includes/modules/front_page/flex_slider.php
 
4) install module
Navigate to your admin front page section and install the module.
 
Enjoy

@@suzgems1
 
what shop version are you using and what usps modification are you working with? there are several.

The manufacturers are displayed using the index.php file so you would check the manufacturers checkbox for that page. On the product_info.php, you would uncheck that checkbox.

Sure Timmy, I'll chime in on this.
 
Last year Jetta saved me and probably a lot of others some serious aggravation by helping get a USPS shipping module working again after the USPS made some changes on their end that basically screwed up the functionality of the existing module. For that I owe her a debt of gratitude, and have come to respect her coding skills.
 
While I see that some others are having problems here and there with a couple of releases she did of late, one with another version of the USPS module and of course the simple checkout module, both have been working for me. The IE issue is something I am aware of through your posts, so I am watching for that, and if necessary may disable simple checkout if I feel the problem is significant on my site. Yet I have to note that to disable the module, I just have to do that in configuration. No major code uninstall and other such torture. How handy, disable by just a setting change.
 
Regarding what's put out here for anyone to use (for free), here's where I've come over the past years since I started with OSC.
 
This forum has many very skilled and expert code writers, yet probably all of them, one time or another made errors in code or advice. Not through negligence or such, but simply because of they way coding works, with its intricacies, dependencies, particularities and so on. I've learned enough over the past few years to come to greatly respect and admire the original and current OSC developers for their extensive skills.
 
My only claim to coding skill, is at one time I was a MS Access developer, using VBA to tweak and nudge Access to do all kinds of neat stuff. It was then I learned about how particular and demanding exact coding can be. So when you think of the OSC spiderweb, calling this, querying that, it's simply amazing that this product is here (for free) to use.
 
Here on the forums I've learned that new releases (and old ones)likely will have bugs here and there. So depending on who is releasing the add on, I will sometimes take the plunge and do the install, knowing full well something may come up that we don't want. So i watch the site, see what's going on with overall functionality, and if anything flags out first try to figure it out myself, but usually posting for help on the support thread.
 
As far as support, I don't know what to say about expectations. I am sure these folks have businesses to run, lives to live, so how much can we expect of them to help us out (for free) with our own particular issues. Yet they do. Maybe its not an immediate response, or perhaps they don't know the immediate solution and need time to do research on the bug/glitch or whatever. Or maybe they'll ask us to try this or that to help them narrow down the source.
 
I try to be careful on asking for too much help especially right off. I try to figure things out myself. I don't want to burn these folks out. And I've seen a few get burned out, but mostly coming back after maybe a breather.
 
Anyway, all said, I am optimisitic for simple checkout, and the eventually Jetta will help us work out bugs, glitches and so on. And all for free.
 
Keep on keepin' on.....

Make sure you did step 4
 

I did "here" first..got through (of course)
Then did "test" .....got banned.
Then did "here" again and still am banned.
 
So for me anyway...it worked.
 
Thanks