Error with the grid

[alex5252]

Notice : Trying to access array offset on value of type null in /home/carpetlandusates/public_html/wp-content/plugins/the-grid/includes/navigation-skin.class.php on line 47

When I create a new grid I receive this error.

This same error also occurs on the following lines in the same file.

48
49
50
51
53
54
55
57
58
59
60
62
63
65
119
120
121
122
123
125
126
127
129
130
131
132
134
135
137
202
203
204
205
207
208
209
210
211
212
214
215
217
219
220
221
222
223
265
266
267
268
270
271
272
273
274
275
277
278
280
282
283
284
285
286
361
362
363
364
365
367
368
369
370
371
372
373
374
375
376
377
378
380
381
382
383
384
385
386
387
388
389
390
442
443
444
445
446
448
449
450
451
452
453
454
455
456
457
458
459
462
463
464
465
466
467
468
469
470
471
472
524
525
526
527
529
530
532
533
534
535

As far as I can tell $tg_nav_colors isn’t defined (or defined to null) in the global scope.

I’m using the most recent version of PHP, WP, The Grid, and Pro.

This error occurs when The Grid is the only plugin activated.

[friech]

Hi @alex5252,

Sorry that you’re having that issue, first please do the basic troubleshooting provided here.

If the issue persists, please provide us login credentials in a secure note so we can take a closer look.

Thanks,

[ruenel]

Hello @alex5252,

Notice : Trying to access array offset on value of type....
This is a PHP Notice that usually display when a certain variable is set to null or not yet initialize. It is displaying because your debug mode is turned ON. To get rid of the PHP notices, please disable the debug mode. You can do this by opening wp-config.php and adding

define('WP_DEBUG', false);

/* That's all, stop editing! Happy blogging. */

When you revisit the page, you should no longer be seeing those PHP Notices.

Kindly let us know how it goes.

[alex5252]

I’ve been using Pro and the Grid for years and I always start of my project by making sure WP_DEBUG is set to true, so that I can see errors while I’m developing.

This is the first time I’ve ever seen that error, and I’m using the most up to date Pro, The Grid, PHP and WP. Furthermore this is not a plugin conflict.

So if older versions of Pro, The Grid, PHP and WP did not produce this error while WP_DEBUG == true, then it stands to reason that an update to one of those four caused the error.

You provide support for two of those, so I thought that maybe you would like to know.

Just because something fails gracefully doesn’t mean its behavior is intended, or even desirable.

It’s not affecting my ability to develop the site, but I thought you’d like to be notified about a potential bug.

[ruenel]

Hello Alex5252,

Thank you for notifying us. Yes, we do support this plugin. We will be reporting this to the creators of the plugin to make them aware of this PHP Notice.

Regards.