I've noticed that this warning is being output in logs constantly

Attempting to set settings on a plugin that doesn't have settings: tablemaker

The tablemaker plugin does not define a settings model and has both hasCpSettings and hasCpSection set to false, what is triggering the error?

It looks like the warning is coming from here: https://github.com/craftcms/cms/blob/2eac9249964ccc553bf841c79b9ee44d58f16b61/src/base/Plugin.php#L189

  • Craft CMS: 3.7.43
  • tablemaker: 2.0.1
  • Which Craft and TableMaker versions? FWIW, TableMaker hasn't seen a commit in 4 years, so it's probably been abandoned at this point. May 31 at 21:22
  • Sorry, Craft CMS 3.7.43 and tablemaker 2.0.1. Yeah tablemaker is abandoned, but doesn't mean it's still needed given there isn't a Craft native way of creating tables with definable columns and rows, without a custom fieldtype. There's promising development for Craft 4 as Verbb.io may take it over. May 31 at 21:37
  • Not able to reproduce, using those versions. Which log files contain the error? Does it show up in the debug bar? Control panel or frontend? May 31 at 22:10
  • It is showing up in the web.log, looks like this 2022-05-31 23:27:34 [-][43903][-][warning][application] Attempting to set settings on a plugin that doesn't have settings: tablemaker May 31 at 22:29
  • Interestingly, on a another environment with only a few plugins enabled I cannot replicate this error, so it would appear something on another project is triggering the warning to be logged. Jun 1 at 6:50

1 Answer 1


I think I've figured it out, it would appear looking at project config that the field settings have been added as plugin settings under the plugins config key, looking at one project:

    enabled: '1'
    licenseKey: null
    schemaVersion: 1.0.0
      columnsAddRowLabel: ''
      columnsInstructions: ''
      columnsLabel: ''
      rowsAddRowLabel: ''
      rowsInstructions: ''
      rowsLabel: ''

Compared to a fresh install:

    edition: standard
    enabled: true
    schemaVersion: 1.0.0

The project which this is happening on was originally a Craft 2 site, so it's possible it needs additional handling to cleanup. Looking at the Craft 2 database, there is indeed a setting key defined on the plugins table.

As these settings are meant to be for the field type, this looks like a mistake at some point, not sure how they've been able to be written to the plugins settings, but they can be cleaned up with a quick migration.


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.