Hi Weigo Thanks very much for what is looking to be a great tool Just wondering if we can have some comments on a tangled installation. Here's what happened
- The installation site has an existing CRM plugin. https://octobercms.com/plugin/ideaverum-crm
- Went through the normal installation procedure -- Added your CRM to the project
- Update process seemed to install just fine
- CRM Pro did not appear
- Removed ideaverum CRM
- Updated. Both CRM Pro and ideaverum CRM installed
- Created a new project and transferred CRM Pro to that project
- Installation did not appear.
- Clear cache / update - still no CRM
Any tips very much appreciated. Looking forward to getting this going Kindest regards Mike
Notice this error in the log Symfony\Component\Debug\Exception\FatalThrowableError: Cannot use object of type Illuminate\Http\Response as array in /var/www/prema/modules/backend/classes/BackendController.php:163 Have tried multiple installs
Hi Mike,
Thank you for your interest in my plugin. I am sorry to hear the installation is giving you some trouble. Let's try and get you sorted.
- Are you running the latest version of OctoberCMS?
- My CRM Pro plugin has some dependencies. Did you install those? (the OctoberCMS dashboard should indicate any issues in the System Status Widget). This would be the most likely problem.
Please note that RainLab.User, RainLab.UserPlus, RainLab.Translate are required for this plugin and that the RainLab.UserPlus plugin now requires RainLab.Location and RainLab.Notify
- Make sure you allow
short_open_tag
in your PHP configuration (default)
If none of these do anything for you:
- You can also try if disabling your other plugins changes anything (in case any of those is somehow creating some conflict).
- Any errors in the logs?
Please do let me know if this helps! If not, please supply the following additional information:
- What version of OctoberCMS are you using?
- What version of PHP?
- What database?
Last updated
We tried an install on a separate instance which has been upgraded. On the associated database this query fails as having a syntax error
create table `briddle_crm_log` (
`id` int unsigned not null auto_increment primary key,
`user_id` int not null,
`description` text not null,
`created_at` timestamp not null,
`updated_at` timestamp not null
) default character set utf8mb4 collate utf8mb4_unicode_ci engine = InnoDB
Error: SQLSTATE[42000]: Syntax error or access violation
System: MySQL version mysql Ver 14.14 Distrib 5.7.30, for Linux (x86_64) using EditLine wrapper Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic
Last updated
Have done quite a lot to check out this issue. Turns out that the crm log schema is trying to set two timestamp fields in the log table, which is apparently illegal in our version of MySQL - see above. ver 5.7
We're looking forward to using this CRM but will be forced to move on if we can't resolve this Any ideas please anyone?
Hi there,
I'm running:
nginx
php@7.4.1.3
mysql@5.7
CMS v1.0.471
I have installed CRM on an existing project, I think I'm having a similar issue. When I run 'check for updates' and update CRM, I get a DB error.
Update failed
"SQLSTATE[42000]: Syntax error or access violation: 1067 Invalid default value for 'updated_at'
(SQL: create table `briddle_crm_log` (`id` int unsigned not null auto_increment primary key,
`user_id` int not null, `description` text not null, `created_at` timestamp not null, `updated_at`
timestamp not null) default character set utf8mb4 collate utf8mb4_unicode_ci engine = InnoDB)"
on line 664 of /Users/responsive/Documents/Valet-
Sites/responsiveweb/vendor/laravel/framework/src/Illuminate/Database/Connection.php
All dependancies are installed as per docs.
Any ideas how I can get this sorted?
Cheers,
Cy
Hi Cy,
Hmmm... this remains a strange issue. It is 01:45 over here but I will look into this for you tomorrow.
Thanks!
Briddle said:
Hi Cy,
Hmmm... this remains a strange issue. It is 01:45 over here but I will look into this for you tomorrow.
Thanks!
Great, thank you.
Hi Cy,
As mentioned by prema770:
This required a fresh OCMS / CRM installation to clear the issue. Maybe plugin contention
I am not working at full capacity right now (my father died a few weeks ago) but I will do my best to resolve this a.s.a.p.
It looks like there is some issue when adding the CRM to a site already using some other plugins (most likely the RainLab.User
plugin) or when not using some required plugins (some sort of looped dependency). I sort of have a general scenario in mind that could play a role here but I do not have a solution to this issue yet (other than a fresh installation). Could you please tell me / confirm to me the names of the general plugins that the site that you are adding Briddle.Crm
to is using (e.g. RainLab.User
, etc.).
Also, most likely, a listener in Briddle.Crm
is probably logging some event before the required table is created. Some sort of looped dependency. So in the meantime:
- Try adding all required plugins before adding
Briddle.Crm
Thank you!
Hi Weigo,
I'm sorry to hear bout your father.
I have tried installing CRM after all required plugins and still no go.
Installed plugins:
- RainLab.Builder
- Indikator.DevTools
- October.Drivers
- Indikator.Backend
- RainLab.Pages
- Renatio.BackupManager
- HeathDutton.Cloudflare
- RainLab.GoogleAnalytics
- Vdlp.Redirect
- Renatio.SeoManager
- OnePilot.Client
- ThePhuc.Tunsecurity
- Frozendo.PagePreview
- RedMarlin.Leafletmap
- Vdlp.SchemaOrg
- RLuders.Cors
- JanVince.SmallExtensions
- ToughDeveloper.ImageResizer
- AlekseyP.GoogleTagManager
- WebVPF.Share
- RainLab.Blog
- RainLab.Translate
- RainLab.User
- Fytinnovations.Helpdesk
- VojtaSvoboda.TwigExtensions
- PolloZen.NextPrevPost
- Rahman.BlogTags
- ReaZzon.Gutenberg
- Code200.Eucookielawmadness
- Responsiv.Campaign
- Briddle.Pageguide
- RainLab.Location
- RainLab.Notify
- RainLab.UserPlus
- Briddle.Crm
Thanks for you help.
Cy
Last updated
Hi Cy,
Thank you.
Ok, so running a couple of different tests here:
TEST 1
- Fresh installation of October (latest version)
- Attach to Project by ID (Project only contains the CRM plugin)
Result:
- The
Briddle.Crm
plugin requiresRainLab.Translate
to be installed before it will work - The
Briddle.Crm
plugin requiresRainLab.User
to be installed before it will work - The
Briddle.Crm
plugin requiresRainLab.UserPlus
to be installed before it will work - The
Briddle.Crm
plugin requiresRainLab.Notify
to be installed before it will work - The
Briddle.Crm
plugin requiresRainLab.Location
to be installed before it will work
After installing the required dependencies:
- No errors, happy user, happy developer
So.... that is both good news and bad news. It is good news because there are no apparent bugs that will cause issues for everybody. It is bad news because this does not help you in any way.
So, let's do another test....
Last updated
TEST 2
Let's try and add a user to RainLab.User
BEFORE adding the CRM.
- Add a user to
RainLab.User
- Remove
Briddle.Crm
- Add
Briddle.Crm
For this test I am running: php@7.3.1 mysql@5.7.24 CMS v1.0.471
Result:
- removing
Briddle.Crm
actually produced a small unrelated error
After fixing this (version 2.2.0):
- No errors, happy user, happy developer
Last updated
TEST 3
Let's try and add the other plugins BEFORE adding the CRM.
- RainLab.Builder
- Indikator.DevTools
- October.Drivers
- Indikator.Backend
- RainLab.Pages
- HeathDutton.Cloudflare
- RainLab.GoogleAnalytics
- Vdlp.Redirect
- OnePilot.Client
- ThePhuc.Tunsecurity
- Frozendo.PagePreview
- RedMarlin.Leafletmap
- Vdlp.SchemaOrg
- RLuders.Cors
- JanVince.SmallExtensions
- ToughDeveloper.ImageResizer
- AlekseyP.GoogleTagManager
- WebVPF.Share
- RainLab.Blog
- RainLab.Translate
- RainLab.User
- VojtaSvoboda.TwigExtensions
- PolloZen.NextPrevPost
- Rahman.BlogTags
- ReaZzon.Gutenberg
- Code200.Eucookielawmadness
- Briddle.Pageguide
- RainLab.Location
- RainLab.Notify
- RainLab.UserPlus
- Briddle.Crm
I did not add paid plugins:
- Responsiv.Campaign
- Renatio.BackupManager
- Renatio.SeoManager
- Fytinnovations.Helpdesk
Result:
- No errors, happy user, happy developer
Last updated
TEST 4
So, after all of this we are no closer to solving this strange issue :(
We are obviousely looking at this the wrong way.
Let's return to the original reported error when adding Briddle.Crm
:
"SQLSTATE[42000]: Syntax error or access violation: 1067 Invalid default value for 'updated_at'
(SQL: create table `briddle_crm_log` (`id` int unsigned not null auto_increment primary key,
`user_id` int not null, `description` text not null, `created_at` timestamp not null, `updated_at`
timestamp not null) default character set utf8mb4 collate utf8mb4_unicode_ci engine = InnoDB)"
on line 664 of /Users/responsive/Documents/Valet-
Sites/responsiveweb/vendor/laravel/framework/src/Illuminate/Database/Connection.php
- The error occurs when creating a table in MySQL (briddle_crm_log)
- The error complains about an invalid default value for the field
updated_at
A quicke search in the forum on octobercms.com leads to the following post, that seems related:
The answer that was added 2 months ago is:
if you faced with sql_mode error , you only need to add 'strict' => false to database config file and mysql array like this : 'mysql' => [ ... 'strict' => false ]; Thanks to justincck .
Last updated
Hi Weigo,
I updated the DB config with 'strict' => 'false
but still the same error.
I will build out a fresh app and pull in the same plugins (including paid) and see how I get on. I'll let you know.
Thanks for testing and your help.
Cheers,
Cy
Hi Weigo,
Version 2.2.1 has resolved install issues on an existing project for me.
I removed the CRM plugin and removed the pipeline_id
column from the user table, then reinstalled the plugin and happy days. No errors.
Thanks so much for the update.
Cheers,
Cy
1-17 of 17