trusty-cms 5.0.5 → 5.0.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (10) hide show
  1. checksums.yaml +4 -4
  2. data/Gemfile.lock +10 -11
  3. data/coverage/index.html +154 -154
  4. data/lib/trusty_cms.rb +1 -1
  5. data/spec/dummy/log/development.log +456 -0
  6. data/spec/dummy/log/test.log +0 -635
  7. metadata +38 -41
  8. data/config/database.yml +0 -4
  9. data/spec/dummy/tmp/cache/747/A70/TrustyCms%3A%3AConfig +0 -0
  10. data/spec/dummy/tmp/cache/85C/FA0/TrustyCms.cache_mtime +0 -1
data/lib/trusty_cms.rb CHANGED
@@ -2,6 +2,6 @@ TRUSTY_CMS_ROOT = File.expand_path(File.join(File.dirname(__FILE__), '..')) unle
2
2
 
3
3
  unless defined? TrustyCms::VERSION
4
4
  module TrustyCms
5
- VERSION = '5.0.5'.freeze
5
+ VERSION = '5.0.6'.freeze
6
6
  end
7
7
  end
data/spec/dummy/log/development.log ADDED
@@ -0,0 +1,456 @@
1
+ DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
2
+
3
+ Being able to do this is deprecated. Autoloading during initialization is going
4
+ to be an error condition in future versions of Rails.
5
+
6
+ Reloading does not reboot the application, and therefore code executed during
7
+ initialization does not run again. So, if you reload TrustyCms::Config, for example,
8
+ the expected changes won't be reflected in that stale Class object.
9
+
10
+ `config.autoloader` is set to `classic`. These autoloaded constants would have been unloaded if `config.autoloader` had been set to `:zeitwerk`.
11
+
12
+ In order to autoload safely at boot time, please wrap your code in a reloader
13
+ callback this way:
14
+
15
+ Rails.application.reloader.to_prepare do
16
+ # Autoload classes and modules needed at boot time here.
17
+ end
18
+
19
+ That block runs when the application boots, and every time there is a reload.
20
+ For historical reasons, it may run twice, so it has to be idempotent.
21
+
22
+ Check the "Autoloading and Reloading Constants" guide to learn more about how
23
+ Rails autoloads and reloads.
24
+ (called from <top (required)> at /Users/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
25
+ DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
26
+
27
+ Being able to do this is deprecated. Autoloading during initialization is going
28
+ to be an error condition in future versions of Rails.
29
+
30
+ Reloading does not reboot the application, and therefore code executed during
31
+ initialization does not run again. So, if you reload TrustyCms::Config, for example,
32
+ the expected changes won't be reflected in that stale Class object.
33
+
34
+ `config.autoloader` is set to `classic`. These autoloaded constants would have been unloaded if `config.autoloader` had been set to `:zeitwerk`.
35
+
36
+ In order to autoload safely at boot time, please wrap your code in a reloader
37
+ callback this way:
38
+
39
+ Rails.application.reloader.to_prepare do
40
+ # Autoload classes and modules needed at boot time here.
41
+ end
42
+
43
+ That block runs when the application boots, and every time there is a reload.
44
+ For historical reasons, it may run twice, so it has to be idempotent.
45
+
46
+ Check the "Autoloading and Reloading Constants" guide to learn more about how
47
+ Rails autoloads and reloads.
48
+ (called from <top (required)> at /Users/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
49
+ DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
50
+
51
+ Being able to do this is deprecated. Autoloading during initialization is going
52
+ to be an error condition in future versions of Rails.
53
+
54
+ Reloading does not reboot the application, and therefore code executed during
55
+ initialization does not run again. So, if you reload TrustyCms::Config, for example,
56
+ the expected changes won't be reflected in that stale Class object.
57
+
58
+ `config.autoloader` is set to `classic`. These autoloaded constants would have been unloaded if `config.autoloader` had been set to `:zeitwerk`.
59
+
60
+ In order to autoload safely at boot time, please wrap your code in a reloader
61
+ callback this way:
62
+
63
+ Rails.application.reloader.to_prepare do
64
+ # Autoload classes and modules needed at boot time here.
65
+ end
66
+
67
+ That block runs when the application boots, and every time there is a reload.
68
+ For historical reasons, it may run twice, so it has to be idempotent.
69
+
70
+ Check the "Autoloading and Reloading Constants" guide to learn more about how
71
+ Rails autoloads and reloads.
72
+ (called from <top (required)> at /Users/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
73
+ DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
74
+
75
+ Being able to do this is deprecated. Autoloading during initialization is going
76
+ to be an error condition in future versions of Rails.
77
+
78
+ Reloading does not reboot the application, and therefore code executed during
79
+ initialization does not run again. So, if you reload TrustyCms::Config, for example,
80
+ the expected changes won't be reflected in that stale Class object.
81
+
82
+ `config.autoloader` is set to `classic`. These autoloaded constants would have been unloaded if `config.autoloader` had been set to `:zeitwerk`.
83
+
84
+ In order to autoload safely at boot time, please wrap your code in a reloader
85
+ callback this way:
86
+
87
+ Rails.application.reloader.to_prepare do
88
+ # Autoload classes and modules needed at boot time here.
89
+ end
90
+
91
+ That block runs when the application boots, and every time there is a reload.
92
+ For historical reasons, it may run twice, so it has to be idempotent.
93
+
94
+ Check the "Autoloading and Reloading Constants" guide to learn more about how
95
+ Rails autoloads and reloads.
96
+ (called from <top (required)> at /Users/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
97
+ DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
98
+
99
+ Being able to do this is deprecated. Autoloading during initialization is going
100
+ to be an error condition in future versions of Rails.
101
+
102
+ Reloading does not reboot the application, and therefore code executed during
103
+ initialization does not run again. So, if you reload TrustyCms::Config, for example,
104
+ the expected changes won't be reflected in that stale Class object.
105
+
106
+ `config.autoloader` is set to `classic`. These autoloaded constants would have been unloaded if `config.autoloader` had been set to `:zeitwerk`.
107
+
108
+ In order to autoload safely at boot time, please wrap your code in a reloader
109
+ callback this way:
110
+
111
+ Rails.application.reloader.to_prepare do
112
+ # Autoload classes and modules needed at boot time here.
113
+ end
114
+
115
+ That block runs when the application boots, and every time there is a reload.
116
+ For historical reasons, it may run twice, so it has to be idempotent.
117
+
118
+ Check the "Autoloading and Reloading Constants" guide to learn more about how
119
+ Rails autoloads and reloads.
120
+ (called from <top (required)> at /Users/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
121
+ DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
122
+
123
+ Being able to do this is deprecated. Autoloading during initialization is going
124
+ to be an error condition in future versions of Rails.
125
+
126
+ Reloading does not reboot the application, and therefore code executed during
127
+ initialization does not run again. So, if you reload TrustyCms::Config, for example,
128
+ the expected changes won't be reflected in that stale Class object.
129
+
130
+ `config.autoloader` is set to `classic`. These autoloaded constants would have been unloaded if `config.autoloader` had been set to `:zeitwerk`.
131
+
132
+ In order to autoload safely at boot time, please wrap your code in a reloader
133
+ callback this way:
134
+
135
+ Rails.application.reloader.to_prepare do
136
+ # Autoload classes and modules needed at boot time here.
137
+ end
138
+
139
+ That block runs when the application boots, and every time there is a reload.
140
+ For historical reasons, it may run twice, so it has to be idempotent.
141
+
142
+ Check the "Autoloading and Reloading Constants" guide to learn more about how
143
+ Rails autoloads and reloads.
144
+ (called from <top (required)> at /Users/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
145
+ DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
146
+
147
+ Being able to do this is deprecated. Autoloading during initialization is going
148
+ to be an error condition in future versions of Rails.
149
+
150
+ Reloading does not reboot the application, and therefore code executed during
151
+ initialization does not run again. So, if you reload TrustyCms::Config, for example,
152
+ the expected changes won't be reflected in that stale Class object.
153
+
154
+ `config.autoloader` is set to `classic`. These autoloaded constants would have been unloaded if `config.autoloader` had been set to `:zeitwerk`.
155
+
156
+ In order to autoload safely at boot time, please wrap your code in a reloader
157
+ callback this way:
158
+
159
+ Rails.application.reloader.to_prepare do
160
+ # Autoload classes and modules needed at boot time here.
161
+ end
162
+
163
+ That block runs when the application boots, and every time there is a reload.
164
+ For historical reasons, it may run twice, so it has to be idempotent.
165
+
166
+ Check the "Autoloading and Reloading Constants" guide to learn more about how
167
+ Rails autoloads and reloads.
168
+ (called from <top (required)> at /Users/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
169
+ DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
170
+
171
+ Being able to do this is deprecated. Autoloading during initialization is going
172
+ to be an error condition in future versions of Rails.
173
+
174
+ Reloading does not reboot the application, and therefore code executed during
175
+ initialization does not run again. So, if you reload TrustyCms::Config, for example,
176
+ the expected changes won't be reflected in that stale Class object.
177
+
178
+ `config.autoloader` is set to `classic`. These autoloaded constants would have been unloaded if `config.autoloader` had been set to `:zeitwerk`.
179
+
180
+ In order to autoload safely at boot time, please wrap your code in a reloader
181
+ callback this way:
182
+
183
+ Rails.application.reloader.to_prepare do
184
+ # Autoload classes and modules needed at boot time here.
185
+ end
186
+
187
+ That block runs when the application boots, and every time there is a reload.
188
+ For historical reasons, it may run twice, so it has to be idempotent.
189
+
190
+ Check the "Autoloading and Reloading Constants" guide to learn more about how
191
+ Rails autoloads and reloads.
192
+ (called from <top (required)> at /Users/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
193
+ DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
194
+
195
+ Being able to do this is deprecated. Autoloading during initialization is going
196
+ to be an error condition in future versions of Rails.
197
+
198
+ Reloading does not reboot the application, and therefore code executed during
199
+ initialization does not run again. So, if you reload TrustyCms::Config, for example,
200
+ the expected changes won't be reflected in that stale Class object.
201
+
202
+ `config.autoloader` is set to `classic`. These autoloaded constants would have been unloaded if `config.autoloader` had been set to `:zeitwerk`.
203
+
204
+ In order to autoload safely at boot time, please wrap your code in a reloader
205
+ callback this way:
206
+
207
+ Rails.application.reloader.to_prepare do
208
+ # Autoload classes and modules needed at boot time here.
209
+ end
210
+
211
+ That block runs when the application boots, and every time there is a reload.
212
+ For historical reasons, it may run twice, so it has to be idempotent.
213
+
214
+ Check the "Autoloading and Reloading Constants" guide to learn more about how
215
+ Rails autoloads and reloads.
216
+ (called from <top (required)> at /Users/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
217
+ DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
218
+
219
+ Being able to do this is deprecated. Autoloading during initialization is going
220
+ to be an error condition in future versions of Rails.
221
+
222
+ Reloading does not reboot the application, and therefore code executed during
223
+ initialization does not run again. So, if you reload TrustyCms::Config, for example,
224
+ the expected changes won't be reflected in that stale Class object.
225
+
226
+ `config.autoloader` is set to `classic`. These autoloaded constants would have been unloaded if `config.autoloader` had been set to `:zeitwerk`.
227
+
228
+ In order to autoload safely at boot time, please wrap your code in a reloader
229
+ callback this way:
230
+
231
+ Rails.application.reloader.to_prepare do
232
+ # Autoload classes and modules needed at boot time here.
233
+ end
234
+
235
+ That block runs when the application boots, and every time there is a reload.
236
+ For historical reasons, it may run twice, so it has to be idempotent.
237
+
238
+ Check the "Autoloading and Reloading Constants" guide to learn more about how
239
+ Rails autoloads and reloads.
240
+ (called from <top (required)> at /Users/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
241
+ DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
242
+
243
+ Being able to do this is deprecated. Autoloading during initialization is going
244
+ to be an error condition in future versions of Rails.
245
+
246
+ Reloading does not reboot the application, and therefore code executed during
247
+ initialization does not run again. So, if you reload TrustyCms::Config, for example,
248
+ the expected changes won't be reflected in that stale Class object.
249
+
250
+ `config.autoloader` is set to `classic`. These autoloaded constants would have been unloaded if `config.autoloader` had been set to `:zeitwerk`.
251
+
252
+ In order to autoload safely at boot time, please wrap your code in a reloader
253
+ callback this way:
254
+
255
+ Rails.application.reloader.to_prepare do
256
+ # Autoload classes and modules needed at boot time here.
257
+ end
258
+
259
+ That block runs when the application boots, and every time there is a reload.
260
+ For historical reasons, it may run twice, so it has to be idempotent.
261
+
262
+ Check the "Autoloading and Reloading Constants" guide to learn more about how
263
+ Rails autoloads and reloads.
264
+ (called from <top (required)> at /Users/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
265
+ DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
266
+
267
+ Being able to do this is deprecated. Autoloading during initialization is going
268
+ to be an error condition in future versions of Rails.
269
+
270
+ Reloading does not reboot the application, and therefore code executed during
271
+ initialization does not run again. So, if you reload TrustyCms::Config, for example,
272
+ the expected changes won't be reflected in that stale Class object.
273
+
274
+ `config.autoloader` is set to `classic`. These autoloaded constants would have been unloaded if `config.autoloader` had been set to `:zeitwerk`.
275
+
276
+ In order to autoload safely at boot time, please wrap your code in a reloader
277
+ callback this way:
278
+
279
+ Rails.application.reloader.to_prepare do
280
+ # Autoload classes and modules needed at boot time here.
281
+ end
282
+
283
+ That block runs when the application boots, and every time there is a reload.
284
+ For historical reasons, it may run twice, so it has to be idempotent.
285
+
286
+ Check the "Autoloading and Reloading Constants" guide to learn more about how
287
+ Rails autoloads and reloads.
288
+ (called from <top (required)> at /Users/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
289
+ DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
290
+
291
+ Being able to do this is deprecated. Autoloading during initialization is going
292
+ to be an error condition in future versions of Rails.
293
+
294
+ Reloading does not reboot the application, and therefore code executed during
295
+ initialization does not run again. So, if you reload TrustyCms::Config, for example,
296
+ the expected changes won't be reflected in that stale Class object.
297
+
298
+ `config.autoloader` is set to `classic`. These autoloaded constants would have been unloaded if `config.autoloader` had been set to `:zeitwerk`.
299
+
300
+ In order to autoload safely at boot time, please wrap your code in a reloader
301
+ callback this way:
302
+
303
+ Rails.application.reloader.to_prepare do
304
+ # Autoload classes and modules needed at boot time here.
305
+ end
306
+
307
+ That block runs when the application boots, and every time there is a reload.
308
+ For historical reasons, it may run twice, so it has to be idempotent.
309
+
310
+ Check the "Autoloading and Reloading Constants" guide to learn more about how
311
+ Rails autoloads and reloads.
312
+ (called from <top (required)> at /Users/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
313
+ DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
314
+
315
+ Being able to do this is deprecated. Autoloading during initialization is going
316
+ to be an error condition in future versions of Rails.
317
+
318
+ Reloading does not reboot the application, and therefore code executed during
319
+ initialization does not run again. So, if you reload TrustyCms::Config, for example,
320
+ the expected changes won't be reflected in that stale Class object.
321
+
322
+ `config.autoloader` is set to `classic`. These autoloaded constants would have been unloaded if `config.autoloader` had been set to `:zeitwerk`.
323
+
324
+ In order to autoload safely at boot time, please wrap your code in a reloader
325
+ callback this way:
326
+
327
+ Rails.application.reloader.to_prepare do
328
+ # Autoload classes and modules needed at boot time here.
329
+ end
330
+
331
+ That block runs when the application boots, and every time there is a reload.
332
+ For historical reasons, it may run twice, so it has to be idempotent.
333
+
334
+ Check the "Autoloading and Reloading Constants" guide to learn more about how
335
+ Rails autoloads and reloads.
336
+ (called from <top (required)> at /Users/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
337
+ DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
338
+
339
+ Being able to do this is deprecated. Autoloading during initialization is going
340
+ to be an error condition in future versions of Rails.
341
+
342
+ Reloading does not reboot the application, and therefore code executed during
343
+ initialization does not run again. So, if you reload TrustyCms::Config, for example,
344
+ the expected changes won't be reflected in that stale Class object.
345
+
346
+ `config.autoloader` is set to `classic`. These autoloaded constants would have been unloaded if `config.autoloader` had been set to `:zeitwerk`.
347
+
348
+ In order to autoload safely at boot time, please wrap your code in a reloader
349
+ callback this way:
350
+
351
+ Rails.application.reloader.to_prepare do
352
+ # Autoload classes and modules needed at boot time here.
353
+ end
354
+
355
+ That block runs when the application boots, and every time there is a reload.
356
+ For historical reasons, it may run twice, so it has to be idempotent.
357
+
358
+ Check the "Autoloading and Reloading Constants" guide to learn more about how
359
+ Rails autoloads and reloads.
360
+ (called from <top (required)> at /Users/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
361
+ DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
362
+
363
+ Being able to do this is deprecated. Autoloading during initialization is going
364
+ to be an error condition in future versions of Rails.
365
+
366
+ Reloading does not reboot the application, and therefore code executed during
367
+ initialization does not run again. So, if you reload TrustyCms::Config, for example,
368
+ the expected changes won't be reflected in that stale Class object.
369
+
370
+ `config.autoloader` is set to `classic`. These autoloaded constants would have been unloaded if `config.autoloader` had been set to `:zeitwerk`.
371
+
372
+ In order to autoload safely at boot time, please wrap your code in a reloader
373
+ callback this way:
374
+
375
+ Rails.application.reloader.to_prepare do
376
+ # Autoload classes and modules needed at boot time here.
377
+ end
378
+
379
+ That block runs when the application boots, and every time there is a reload.
380
+ For historical reasons, it may run twice, so it has to be idempotent.
381
+
382
+ Check the "Autoloading and Reloading Constants" guide to learn more about how
383
+ Rails autoloads and reloads.
384
+ (called from <top (required)> at /Users/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
385
+ DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
386
+
387
+ Being able to do this is deprecated. Autoloading during initialization is going
388
+ to be an error condition in future versions of Rails.
389
+
390
+ Reloading does not reboot the application, and therefore code executed during
391
+ initialization does not run again. So, if you reload TrustyCms::Config, for example,
392
+ the expected changes won't be reflected in that stale Class object.
393
+
394
+ `config.autoloader` is set to `classic`. These autoloaded constants would have been unloaded if `config.autoloader` had been set to `:zeitwerk`.
395
+
396
+ In order to autoload safely at boot time, please wrap your code in a reloader
397
+ callback this way:
398
+
399
+ Rails.application.reloader.to_prepare do
400
+ # Autoload classes and modules needed at boot time here.
401
+ end
402
+
403
+ That block runs when the application boots, and every time there is a reload.
404
+ For historical reasons, it may run twice, so it has to be idempotent.
405
+
406
+ Check the "Autoloading and Reloading Constants" guide to learn more about how
407
+ Rails autoloads and reloads.
408
+ (called from <top (required)> at /Users/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
409
+ DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
410
+
411
+ Being able to do this is deprecated. Autoloading during initialization is going
412
+ to be an error condition in future versions of Rails.
413
+
414
+ Reloading does not reboot the application, and therefore code executed during
415
+ initialization does not run again. So, if you reload TrustyCms::Config, for example,
416
+ the expected changes won't be reflected in that stale Class object.
417
+
418
+ `config.autoloader` is set to `classic`. These autoloaded constants would have been unloaded if `config.autoloader` had been set to `:zeitwerk`.
419
+
420
+ In order to autoload safely at boot time, please wrap your code in a reloader
421
+ callback this way:
422
+
423
+ Rails.application.reloader.to_prepare do
424
+ # Autoload classes and modules needed at boot time here.
425
+ end
426
+
427
+ That block runs when the application boots, and every time there is a reload.
428
+ For historical reasons, it may run twice, so it has to be idempotent.
429
+
430
+ Check the "Autoloading and Reloading Constants" guide to learn more about how
431
+ Rails autoloads and reloads.
432
+ (called from <top (required)> at /Users/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)
433
+ DEPRECATION WARNING: Initialization autoloaded the constants TrustyCms::Config, Admin, Admin::RegionsHelper, ApplicationHelper, DeviseHelper, ApplicationController, Admin::ResourceHelper, Admin::ResourceController, Admin::LayoutsHelper, Admin::LayoutsController, MultiSite::SiteChooserHelper, Admin::SnippetsController, ActionText::ContentHelper, and ActionText::TagHelper.
434
+
435
+ Being able to do this is deprecated. Autoloading during initialization is going
436
+ to be an error condition in future versions of Rails.
437
+
438
+ Reloading does not reboot the application, and therefore code executed during
439
+ initialization does not run again. So, if you reload TrustyCms::Config, for example,
440
+ the expected changes won't be reflected in that stale Class object.
441
+
442
+ `config.autoloader` is set to `classic`. These autoloaded constants would have been unloaded if `config.autoloader` had been set to `:zeitwerk`.
443
+
444
+ In order to autoload safely at boot time, please wrap your code in a reloader
445
+ callback this way:
446
+
447
+ Rails.application.reloader.to_prepare do
448
+ # Autoload classes and modules needed at boot time here.
449
+ end
450
+
451
+ That block runs when the application boots, and every time there is a reload.
452
+ For historical reasons, it may run twice, so it has to be idempotent.
453
+
454
+ Check the "Autoloading and Reloading Constants" guide to learn more about how
455
+ Rails autoloads and reloads.
456
+ (called from <top (required)> at /Users/donavin/Documents/development/trusty-cms/spec/dummy/config/environment.rb:5)