Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #1103683
    Beda Schmid
    Guest

    Hello, this is Beda, from Toolset Support.

    There is a long standing attempt from Toolset side to contact developers at Kriesi, so to report an issue with the Enfold Theme, however we seem to write in to the wrong email, as we get no reply :)

    Hence, I am trying here to reach out and point to the issue happening with Toolset Views and the Enfold theme – since the Enfold Theme uses different functions to display content depending on its type, and Toolset only supports the_content() generally, or other clear content renderer, Toolset Views cannot design the Content at all if rendered with the Theme.

    We wanted to suggest something to fix this, however, we would need to know where to send the suggestions to.

    #1103702

    Hi Beda,

    Thanks for contacting us!

    We have discussed Toolset compatibility with the team and Kriesi and seems like we are going to need to add config folder for Toolset in Enfold to make Toolset compatible with Enfold out of the box however we are not really leaning towards to that idea to be honest.

    I have seen this post – https://toolset.com/errata/views-slider-does-not-work-when-the-enfold-theme-is-active/ and alternative to filter provided in the post is going to Enfold theme options > Performance tab and choose to always load “Self hosted videos and audio features (WP-Mediaelement scripts)”. I am afraid this is currently the only solution we have for the issue.

    Best regards,
    Yigit

    #1103880
    Beda Schmid
    Guest

    Hello Yigit, it is very nice to read from you.

    I can assure you’d not need to add any Configuration Files to your theme, for the issues I have in mind which I’d like to discuss.
    The Config File you mention is required if you’d like to make a theme “CPT Ready”, this means, you can add a file with all options of your theme, so later in Toolset settings for a Layout, for example, you can manipulate these settings – however, that’s not what I reached out for :)

    Related to the erratum you mentioned, thanks for the inforamtions!
    I have added them to the entry so the users can consider both options.

    The issue I wanted to discuss further is related to Enfold’s Content Render Functions. It seems Enfold theme uses several different functions to display content depending on its type.

    Examples:
    – In page (loop-page.php) the_content is used
    – In some of the single post files, like single-event.php the_content is used.
    – In some others, as single Post (also rendering Custom Posts) avia_markup_helper() is used.

    Toolset Views can replace the_content and any other custom content render function with a Content Template. Content Templates are like “Layouts” you can design, and they replace the Post Body (usually rendered thru the_content())

    Since the Enfold Theme does not always use the_content() and the custom Content Render Function used instead is something like WP_Hook::apply_filters (last time I debugged this), in those cases Views cannot apply it’s Content Templates – which means the users cannot design the post bodies with it.

    Views would expect either the_content, or any other dedicated function to display the content but it will not accept generic PHP functions or auxiliar WordPress functions like require, require_once, include, include_once, locate_template, load_template, apply_filters, call_user_func_array.

    I wanted to reach out in the name of our common clients/users so to clarify whether we could work out a solution together.
    If you’d be willing to cooperate in a solution, I’d like to connect by email if this is possible. I would then show you the issue on an online install and eventually, we could add a small compatibility layer?

    Thank you for your time and consideration :)

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.