Log message #4151946

# At Username Text
# Jun 16th 2018, 02:31 Guest82403 This is with whatever cakephp/app chooses as the default version, and dereuromark/cakephp-ide-helper was listed in the recommend block.
# Jun 16th 2018, 02:21 dereuromark go oldschool
# Jun 16th 2018, 02:21 dereuromark Sounds like u are using the new plugin loading with plugins that dont do this yet.
# Jun 16th 2018, 01:47 Guest82403 t be found. Ensure your autoloader is correct." Apparently I missed a setup step.
# Jun 16th 2018, 01:47 Guest82403 So I haven't used CakePHP in years, and I have no idea how to debug a broken plugin. Tried to enable dereuromark/cakephp-ide-helper. It's in the composer.json and the vendor directory, but if I add it to Application.php attempting to use bin/cake returns "PHP Fatal error: Uncaught InvalidArgumentException: The plugin class `IdeHelper\Plugin` canno
# Jun 15th 2018, 22:33 squeeze route is missing on customer prefix i guess ?
# Jun 15th 2018, 22:27 mike__ https://thepasteb.in/p/2RhK4zD558Qu4
# Jun 15th 2018, 22:23 mike__ when i load the view i have the follow error
# Jun 15th 2018, 22:22 mike__ the second form is with url option ( 'url' => ['controller' => 'Deactivations', 'action' => 'index' ])
# Jun 15th 2018, 22:21 mike__ the first form is from view's controller ( users )
# Jun 15th 2018, 22:20 mike__ i want to do 2 forms into the same view
# Jun 15th 2018, 22:20 mike__ i have some problem with formhelper
# Jun 15th 2018, 22:16 mike__ hello everybody
# Jun 15th 2018, 21:04 itmpls anyone use cakephp-subdomains or similar in 3.6+ for a dynamic subdomain setup?
# Jun 15th 2018, 20:46 blackjccl File uploaded https://cakesf.slack.com/files/U5V7HDBHC/FB8C9SK28/-.php / https://slack-files.com/T053DPNCM-FB8C9SK28-09e61014ba
# Jun 15th 2018, 20:45 blackjccl my code
# Jun 15th 2018, 20:45 blackjccl "Cannot get an empty property"
# Jun 15th 2018, 20:45 blackjccl the error is as follows
# Jun 15th 2018, 20:44 blackjccl I have the following problem when I want to save in the same entity several times
# Jun 15th 2018, 20:43 blackjccl hi community
# Jun 15th 2018, 19:22 tewinkel quit
# Jun 15th 2018, 19:16 tewinkel If I view a single organisation, I see all deliveries, but I see only the ids of driver, fruit and supermarket. I would like to see the names.
# Jun 15th 2018, 19:15 lorenzo @itmpls I also vote for single db for all tenants
# Jun 15th 2018, 19:14 tewinkel My main table is organisation. Every organisation has a list of delivery-actions, which consist of a combination of fruit, driver and supermarket.
# Jun 15th 2018, 19:12 tewinkel Yes sorry, dont know how to format my question properly
# Jun 15th 2018, 19:12 mikesmoniker pastebin that?
# Jun 15th 2018, 19:09 tewinkel test\ntest
# Jun 15th 2018, 19:07 tewinkel ruits. I want to see the names
# Jun 15th 2018, 19:07 tewinkel I have these tables: fruits ------- id name drivers ------- id name supermarkets ------------- id name deliveries ------------- fruit_id driver_id supermarket_id organisation_id organisations -------------- id name .... many fields --- I have baken the source for my application. If I take a look at a single organisation, i can see all deliveries belonging to this organisation. But the table of deliveries contains only the
# Jun 15th 2018, 19:07 itmpls ask away
# Jun 15th 2018, 19:06 tewinkel Hello! I need some help concerning table joins. Are there any experts round here?
# Jun 15th 2018, 18:32 itmpls probably going with a single db for simplicity and i'm not gonna have hundreds of tenants or anything
# Jun 15th 2018, 18:29 admad @mikesmoniker very insightful response :+1:
# Jun 15th 2018, 18:27 itmpls thank you @mikesmoniker
# Jun 15th 2018, 18:20 itmpls ah ok
# Jun 15th 2018, 18:17 mikesmoniker Final thought: if you do go with multiple DBs, please research how to properly encrypt their individual credentials. Don’t just throw them in a table somewhere in the clear. That seems to occur in the wild way more than it should.
# Jun 15th 2018, 18:16 mikesmoniker But I wouldn’t necessarily advise designing _for_ those kinds of horrible cases. Presumably you have good design, tests, etc. to mitigate those risks.
# Jun 15th 2018, 18:16 mikesmoniker The times I did multi-DB didn’t really fall under those scenarios, but the benefits included things like a breach/security issue (in theory) only put one customer at-risk, it was virtually impossible for a bug to cause one customer to see another’s data, and if we screwed something up big time we could roll back a single customer’s DB without having to stitch together data.
# Jun 15th 2018, 18:14 mikesmoniker My advice is a single DB for all tenants unless you have a compelling reason not to (e.g. serious privacy/compliance concerns, scaling to millions of customers, etc.). It’s way simpler.
# Jun 15th 2018, 18:13 mikesmoniker A couple things to consider: would you pair a codebase with each db. (e.g. one instance of the app to many DBs, or one-to-one? The former makes DB migrations complicated.) Do you need to do complex cross-tenant reporting.
# Jun 15th 2018, 18:11 itmpls any recommendations specifically from experience?