Problem/Motivation

So after installation, when I run cforge/setup in the browser, I get a white screen and a list of PHP error messages in the log.

I can get around it by toggling some of the options off, but then there are problems with the site, like when you try to make a push transaction there's no field for the second party.

I showed the site to the group yesterday at our first meeting and we're excited to get started. Thanks for all the work you're doing on this.

Message Notice: Undefined index: project in Drupal\cforge\Setup->buildForm() (line 154 of /var/www/html/okanogantrades/web/profiles/cforge/src/Setup.php)
#0 /var/www/html/okanogantrades/web/core/includes/bootstrap.inc(347): _drupal_error_handler_real()
#1 /var/www/html/okanogantrades/web/profiles/cforge/src/Setup.php(154): _drupal_error_handler()
#2 [internal function]: Drupal\cforge\Setup->buildForm()
.
Severity Notice
Warning: Use of undefined constant SMALLAD_CATEGORIES - assumed 'SMALLAD_CATEGORIES' (this will throw an Error in a future version of PHP) in Drupal\cforge\Setup->submitForm() (line 292 of /var/www/html/okanogantrades/web/profiles/cforge/src/Setup.php)
#0 /var/www/html/okanogantrades/web/core/includes/bootstrap.inc(347): _drupal_error_handler_real()
#1 /var/www/html/okanogantrades/web/profiles/cforge/src/Setup.php(292): _drupal_error_handler()
#2 [internal function]: Drupal\cforge\Setup->submitForm()

Severity Warning
TypeError: Argument 1 passed to Drupal\cforge\Setup::vocabImportRecursive() must be an instance of Drupal\taxonomy\Entity\Vocabulary, null given, called in /var/www/html/okanogantrades/web/profiles/cforge/src/Setup.php on line 300 in Drupal\cforge\Setup->vocabImportRecursive() (line 393 of /var/www/html/okanogantrades/web/profiles/cforge/src/Setup.php)
#0 /var/www/html/okanogantrades/web/profiles/cforge/src/Setup.php(300): Drupal\cforge\Setup->vocabImportRecursive()
#1 [internal function]: Drupal\cforge\Setup->submitForm()
.

Comments

amysragbag created an issue. See original summary.

matslats’s picture

matslats commented
Issue summary: View changes
Status: Active » Needs review

Hi Amy,
I remember we had some correspondence in 2008 when you were accounting for 'ragbags'.
The warnings you cite have all been fixed in the last few days, so make sure you run
composer update --no-dev
and visit cforge/setup and run that final part of the setup again.
I think the last warning is what led to the failure (white screen) which should be documented in your server error log, but which I think won't happen once smallads and cforge are up to date.
Matthew

amysragbag’s picture

amysragbag commented

Hi Matt,

I ran the composer update --no-dev and it updated geofield. This is on a fresh install that I did yesterday.

The white screen seems to have to do with ticking GDPR compliance and English LETS. If I leave GDPR blank I get a white screen, and if I tick it I get a notice that I've made an illegal choice. I am in the US but I filled out the GDPR compliance page anyway, and now the cforge/setup page is 'not found.'

I'm still not seeing a field for the second party to push transactions.

If I start over and do a fresh install, should I use the composer file you gave me here https://www.drupal.org/project/cforge/issues/3299585#comment-14623314 or install it a different way?

Thanks!

Laura

amysragbag’s picture

amysragbag commented

Hi Matthew, I wonder if it makes a difference how I created the database? I used:

CREATE DATABASE okanogantrades CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;

and then I tried it with utf8mb4_general_ci;

and got the same results.

It was the English LETS option that gav me the white screen this time and I'm pretty sure it's associated with this error:
TypeError: Argument 1 passed to Drupal\cforge\Setup::vocabImportRecursive() must be an instance of Drupal\taxonomy\Entity\Vocabulary, null given, called in /var/www/html/okhighlandtrades/web/profiles/cforge/src/Setup.php on line 300 in Drupal\cforge\Setup->vocabImportRecursive() (line 393 of /var/www/html/okhighlandtrades/web/profiles/cforge/src/Setup.php)

That's not a problem for me, just FYI. I think when we figure out how to have both payer and payee fields visible on push transactions we will be ready to start recording our trades. We are very grateful.

Was it the same issue all those years ago, and do you remember how we fixed it? I think there was something missing or misconfigured in my database? That was so long ago.

matslats’s picture

matslats commented

Hi
I found this vocabulary error but I guess it won't filter through to you till I release another version of Hamlets.
in profiles/cforge/src/Setup.php lines 291 and 296 you should replace
SMALLAD_CATEGORIES
with
SMALLAD_CATEGORIES_VID
Your database character set and collation is nothing to do with it.

> Was it the same issue all those years ago, and do you remember how we fixed
> it? I think there was something missing or misconfigured in my database? That
> was so long ago.
Everything is always a work in progress. My transaction form designs are trying to do basically the same thing, which is tricky in Drupal but all the code has changed a lot.
I've been facing a lot of problems with my local instance, but I'm going to look at the missing field now.

matslats’s picture

matslats commented

On admin/accounting/transactions/form-display/credit
in the template section, swop {payer} and {payee} and everything will work.

amysragbag’s picture

amysragbag commented

That works! Thank you so much! <3

amysragbag’s picture

amysragbag commented
Status: Needs review » Closed (works as designed)