Priscillia Umeakuekwe
Priscillia Umeakuekwe
hi @brylie can i comment on this issue? i replicated the steps and saw the error and its in relation to the issue #186 
Thats fine but i will want to know if the notice has an after effect on the widget functionality, or by getting rid of the notice solves the issue?
I am certain with a better understanding of issue #186 and fixing the notice we can ascertain the after effect of this issue.
hi @brylie i will love too work on this issue thanks.
@brylie can i know which module this issue is referring to.
alright @brylie i understand now will look at it
@brylie i did some research on this issue and the notice displays due to the deps checks in the ./wp-includes/widgets.php file 
so i made an edit in the ./wp-includes/default-filters.php file by commenting out the action that displays the error, and when i reloaded my localhost i didn't get the error ...
although i am still in search for the wp-enqueue-script that might have been hooked wrongly. my update for now thanks.