I enabled the module, and got this message:

warning: Missing argument 1 for cafepress_menu() in /home/socalmov/public_html/sites/all/modules/cafepress/cafepress.module on line 81.

Comments

kirkcaraway’s picture

Same here. I also can't find the configurations page (probably due to the error).

jriedel’s picture

Yes something is not right in the now offical version. I had to back off to the unoffical version I had.

One thing that I noticed right away a subdirectory called classes and the file in that directory are missing from the build.

It looks like line 81 is stuff that got added/chnaged in the code cleanup, and it has to do with the admin menus so that also explains #1 from kirkcaraway.

I also got an error trying to hit my products page.

dir(images/cafepress) [function.dir]: failed to open dir: No such file or directory in /home/jriedel/public_html/ec_site/sites/all/modules/cafepress/cafepress.module on line 267.

ebeyrent’s picture

Assigned: Unassigned » ebeyrent
ebeyrent’s picture

Hey there -

Use this release:

http://drupal.org/node/679034

This will become official soon...

CinemaSaville’s picture

Version: 6.x-1.0 » 6.x-1.0-alpha1

Got this message when installing new alpha:
warning: Invalid argument supplied for foreach() in /home/socalmov/public_html/sites/all/modules/cafepress/cafepress.module on line 353.

And image and price info for product in block doesn't show up, and page is completely devoid of products or any css. So it looks like you might need to work on this a bit more. But keep going. I'm sure you'll get it, and thanks for the effort.

dharmanerd’s picture

Change line 81 to function cafepress_menu($may_cache=false) {

CinemaSaville’s picture

Did that, now I get:
Fatal error: Call to a member function read() on a non-object in /home/***/public_html/sites/all/modules/cafepress/cafepress.module on line 268

ebeyrent’s picture

Priority: Normal » Critical

$may_cache is not part of the Drupal 6 API - see http://api.drupal.org/api/function/hook_menu/6.

I just committed a number of changes, and am not seeing any errors on install. Give the latest dev version a try and let me know how it goes!

Katrina B’s picture

I can confirm that the error is still present in 6.x-1.0 but not in the current dev version.