6 posts / 0 new
Last post
spensort
spensort's picture
Offline
Last seen: 4 months 2 weeks ago
Joined: 03/11/2017
Undefined index: webcomponents

Hi,

I have been getting this error report, but, really do not understand what it is on about or, what to do about it.

Can anyone help?

---Error log report:--- Type php Date Tuesday, May 8, 2018 - 14:04 User Chris Spencer Location http://www.mindsets.eu/pedles/dev_d7-opigno/admin/reports/status Referrer http://www.mindsets.eu/pedles/dev_d7-opigno/admin/reports Message NOTICE: Undefined index: webcomponents in WEBCOMPONENTS_POLYMER_WEBCOMPONENT_ATTACHED_FILES_ALTER() (line 210 of /HOME/LIIKANJITSU/PUBLIC_HTML/MINDSETS.EU/PEDLES/DEV_D7-OPIGNO/SITES/ALL/MODULES/WEBCOMPONENTS/MODULES/WEBCOMPONENTS_POLYMER/WEBCOMPONENTS_POLYMER.MODULE). Severity notice Hostname 85.156.51.243

Operations

Kr, Chris

spensort
spensort's picture
Offline
Last seen: 4 months 2 weeks ago
Joined: 03/11/2017
Warning, Warning Will Robinson!...

Hi,

I have been adding extension contrib modules and recently started getting the following warning message out of the blue.

Warning: Invalid argument supplied for foreach() in opigno_class_app_views_query_alter()(line 408 of /home/liikanjitsu/public_html/mindsets.eu/pedles/dev_d7-opigno/profiles/opigno_lms/modules/opigno/opigno_class_app/opigno_class_app.module).

I have not touched the Opigno profile/apps, nor the views module so far. I disabled one of the modules and the error does not seem to have reappeared. Neither has it appeared again after re-enabling the same module. I did this because the Devsite is a clone of the live site which has not got the same error message(s).

Now instead I have been getting the following error message on the devsite only:

TypeError: Argument 2 passed to SelectQuery::fields() Error encountered when running "configuration save" on the Devsite

TypeError: Argument 2 passed to SelectQuery::fields() must be of the type array, null given, called in /home/liikanjitsu/public_html/mindsets.eu/pedles/dev_d7-opigno/includes/entity.inc on line 317 in SelectQuery->fields() (line 1316 of /home/liikanjitsu/public_html/mindsets.eu/pedles/dev_d7-opigno/includes/database/select.inc).

The website encountered an unexpected error. Please try again later

The only error/warning message that is common to both sites is:

Warning: array_keys() Everytime I run the save configuration or run the update script via the modules page link…

Warning: array_keys() expects parameter 1 to be array, null given in drupal_schema_fields_sql() (line 7249 of /home/liikanjitsu/public_html/mindsets.eu/pedles/dev_d7-opigno/includes/common.inc).

I checked the common.inc in both live and dev site filesystems against the original downloads, and they appear to be correct, so the issue is in the database or the hosting environment.

Current Workaround = Run update.php a second time from the browser command line and all appears to return to normal

A further notice in the log reports is:

Notice: Undefined index: webcomponents in webcomponents_polymer_webcomponent_attached_files_alter() (line 210 of /home/liikanjitsu/public_html/mindsets.eu/pedles/dev_d7-opigno/sites/all/modules/webcomponents/modules/webcomponents_polymer/webcomponents_polymer.module).

This latest notice, however, appears to be unrelated to the main issue described above.

The hosting support keep pointing the finger at Drupal, however, given that the two sites dev and live are identicle (devsite originally a clone of the live site and extended in parallel), this seems to hold little credence. Then last week, I put down tools on Thursday to go on long weekend holiday, all seem to be well and working in terms of the Composer tool etc. When I returned on Monday, Composer was no longer working and could not find the vendor directory it had created. I tried to rebuild the .json file using the rebuild option from within Composer Manager, but that did not seem to affect the .json file, which had effectively been wiped clean apart from some basic generic scripts. Not only the .json file and been wiped down, but also a backup file under another name that composer could not have accessed, seemed to have suffered the same fate. My composer app is in the directory above the drupal sites, and hence not within Drupal remit. I have since managed to rebuild the .json file and make it run, albeit without the previous venbor directory require listing.

The latest error message to appear in addition to the common.inc is:

EntityMalformedException EntityMalformedException: Missing bundle property on entity of type file. in entity_extract_ids() (line 7932 of /home/liikanjitsu/public_html/mindsets.eu/pedles/dev_d7-opigno/includes/common.inc).

The website encountered an unexpected error. Please Try Again later

When I tried to enable the file_entity and apps_compatbible modules, it just suddenly started to magically appear and causes a fatal error that I cannot recover from except by restoring to previous back-up (registry_rebuild did not work this time). I then restored to a slightly earlier back-up that I know was working, re-installed the captcha and apps-compatible modules again (but not enabled), and tried again with the Captcha module and got the same result, all when running the update script from the browser as previously. So it now seems not to matter what the contrib module is, I cannot enable any extension contrib modules.

All the above events may be unrelated and coincidental, but, just to be sure I have mentioned them in case the hosting environment has something to do with these strange but regular occurences and error messages.

Any thoughts as to what might be going on here, or the root cause of these phenomena?

Kr,

Chris

axel
Offline
Last seen: 4 days 14 hours ago
Staff
Joined: 09/25/2013
Hi Chris,

Hi Chris,

Notices aren't important at all, it's just some information, without any impact for your Opigno instance.

Same for warnings, they have no impact.

What was the message of the fatal error you could not recover. This is the one that would be interesting to make a diagnosis.

It's impossible to make a diagnosis from the information above, a complete investigation should be done.

It's possible that additional contrib modules aren't fully compliant with Opigno.

Make sure to clear all caches after installing an additional contrib module.

Best regards,

spensort
spensort's picture
Offline
Last seen: 4 months 2 weeks ago
Joined: 03/11/2017
File Entity causing Fatal Error

Hi,

I am trying to build and extend my site based on the Opigno for Drupal 7 distribution to use entities and uuid reference linking as much as possible to increase compatibility with future D8 upgrade as well as improve the current referencing and content reuse capabilities within the core opigno lms and in the collaborative workspaces and general homepages surrounding / connected with it. I.e. I am trying to build a truly entity / object orient learning management system that makes use of entities of all kinds, including 'Paragraphs' and other content snippits/elements from related content to rich media components.

To this end, I tried to extend the site with the module 'File Entity' that is needed by several other extension modules I would like to use, but, each time it seems to cause a Fatal Error or "Can't connect to site at this time' message and I am unable to access the site again even after running both registry_rebuild and update.php from the browser window command line.

I have already upgraded my hosting service to deal with the previous error messages I earlier reported that appeared to be due to resource limitations, which, seems to have solved most of the problems thus far - so this seems an unlikely cause this time.

Can anyone tell me if there is a Fatal compatibility issue between 'File Entity' module and Opigno, or is there some other solution/work-around?

Kr, Chris

James Aparicio
James Aparicio's picture
Offline
Last seen: 1 week 4 days ago
Staff
Joined: 10/30/2013
Hi spensort,

Hi spensort,

You have the error itself? Check the server logs and the db logs.

 

Best regards

spensort
spensort's picture
Offline
Last seen: 4 months 2 weeks ago
Joined: 03/11/2017
File Entity Error: 503 error & resource problems?

Hi James,

No, not exactly. I had to restore the site and then succeeded in adding many other entity modules instead. When I tried to enable the File Entity module again yesterday (26.6.) , I got the same result: ERROR: The website encountered an unexpected error. Please try again later.

I ran both update.php and registry-rebuild but, neither solved the problem.

The error_log file within the drupal site root directory shows no errors at all after 15.6. I looked at the metrics on the hosting site c-panel, but that is also empty. I asked them about it and they said it appears to be a 503 error which the c-panel error report does not log.

They are suggesting it is a resource problem, but one probably caused by the File_System module. I have upgraded my service and resources twice in the last month and am now operating on a not so cheap business account with own server. So far adding contrib modules one at a time has remained well within my resource parameters.

Strange things (probably red herrings) happening such as the ffmpeg module in php settings has reappeared. It disappeared after I switched from php 5.6 to php7 at the hosts suggestion/request. It seems to be back again! I have also been consistently getting the following index missing report when running update scripts etc...: "Notice: Undefined index: drupal in update_requirements() (line 35 of /home/liikanjitsu/public_html/mindsets.eu/pedles/lol_opigno-d7/modules/update/update.install)." However, it is not clear to me if this occurred during restore or a cron run, but, the following error reports/notices do appear in every cron job: ultimate_cron 2018-06-27 10:49 Error running cer_entity_settings_cron: PDOException:... Anonymous (not verified)
php 2018-06-27 10:49 Warning: Illegal offset type in isset or empty in... Anonymous (not verified)
php 2018-06-27 10:49 Warning: Illegal offset type in isset or empty in... Anonymous (not verified)
ultimate_cron 2018-06-27 10:49 Error running composer_manager_sa_cron: SensioLabs... Anonymous (not verified)

They could only recommend searching community documentation for information on 503 errors + resource issues. I am still searching the documentation and forums for further information on similar problems.

Kr, Chris