• Resolved marikamitsos

    (@marikamitsos)


    Hello,
    Just wanted to try out your plugin (v.2.2.7) on a site of ours using WordPress v4.7.5 , Linux server with PHP v5.6.30
    All we did was activate the plugin and went over to Tools/Child Themes.
    Checked our error-log and found:

    Jul 09, 22:28:05
    PHP Warning: Invalid argument supplied for foreach() in /wp-content/plugins/child-theme-configurator/includes/classes/CSS.php on line 1946
    Jul 09, 22:28:05
    PHP Warning: preg_grep() expects parameter 2 to be array, boolean given in /wp-content/plugins/child-theme-configurator/includes/classes/CSS.php on line 1945
    Jul 09, 22:28:05
    PHP Warning: array_search() expects parameter 2 to be array, boolean given in /wp-content/plugins/child-theme-configurator/includes/classes/CSS.php on line 502
    Jul 09, 22:28:04
    PHP Warning: array_flip() expects parameter 1 to be array, boolean given in /wp-content/plugins/child-theme-configurator/includes/classes/CSS.php on line 318
    Jul 09, 22:28:04
    PHP Warning: asort() expects parameter 1 to be array, boolean given in /wp-content/plugins/child-theme-configurator/includes/classes/CSS.php on line 314
    Jul 09, 22:28:03
    PHP Warning: array_values() expects parameter 1 to be array, boolean given in /wp-content/plugins/child-theme-configurator/includes/classes/CSS.php on line 1954

    As you can see it all happened within 1 second.
    The same thing happens very time we re-visit the page.
    Could you please help? Any ideas?

    thanks

    PS: Needless to say we didn’t even try to test further after that 🙁

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter marikamitsos

    (@marikamitsos)

    Happy to.
    Like what though?

    Plugin Author lilaeamedia

    (@lilaeamedia)

    I need to find out what makes your WordPress so special that it breaks the configurator and would rather do that off this forum. 🙂

    Plugin Author lilaeamedia

    (@lilaeamedia)

    Never mind. This is affecting all users. Thanks for the report.

    Look for an update shortly.

    Plugin Author lilaeamedia

    (@lilaeamedia)

    This has been addressed in v2.2.8. Please let me know if you require further assistance.

    Thanks,

    –JF

    • This reply was modified 6 years, 9 months ago by lilaeamedia.
    Thread Starter marikamitsos

    (@marikamitsos)

    This seems to correct the issue.
    No more PHP warnings.

    We did notice something else though.
    Upon re-configuration of a child theme, all comments from style.css have disappeared.
    We would like to keep our comments. Is this normal behaviour or an option at the settings?

    Plugin Author lilaeamedia

    (@lilaeamedia)

    From the caveats:

    Arbitrary comments are not supported. Providing a high level of flexibility for previewing and modifying custom styles requires a sophisticated parsing system. Maintaining comments that are bound to any particular element in the stylesheet is prohibitively expensive compared to the value it would add. Although we are working to include this as an option in the future, currently all comments are stripped from the child theme stylesheet code.

    • This reply was modified 6 years, 9 months ago by lilaeamedia.
    Thread Starter marikamitsos

    (@marikamitsos)

    Thank you for the quick reply,

    A way to go around it would probably be to have an option to create a back-up file preserving the comments.
    Just a thought.

    thanks again,
    Marikamitsos

    PS: marking the topic resolved

    Plugin Author lilaeamedia

    (@lilaeamedia)

    When you configure an existing child theme, CTC creates a backup of the existing stylesheet named style.ctcbackup.css. It can be viewed from the theme editor.

    It is used for the restore option.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Abundance of PHP warnings just by visiting Tools/Child Themes’ is closed to new replies.