Okay
  Public Ticket #3664077
Salient v. > 16.1.3 Bug
Open

Comments

  • purchasing416 started the conversation

    Updating the "Salient" theme to version 16.1.3 creates a display issue in the blog section. We see the names of WordPress users under the articles (see attachments). Usernames should not be public, and despite modifying the Meta settings, the information still appears. We performed a ROLL-BACK to avoid the issue, but we cannot keep the old version of the plugin forever.

    Attached files:  MicrosoftTeams-image (38).png
      3f072b2f-6b4c-4e85-99d8-209af7d605f2.png

  •  8,527
    Tahir replied

    Hey Again,

    Please update to the Latest Salient Theme Version.

    The current version of the theme is 16.2.2 and the current version of the page builder is 7.6 .

    Here's the documentation on the available methods for updating Salient: http://themenectar.com/docs/salient/updating-salient/#methods 

    To get a list of Bug Fixes and new Feature addons in the Latest Theme updates view change log here http://themenectar.com/changelogs/salient.html .

    Thanks.


    ThemeNectar Support Team 

  • purchasing416 replied

    Hello Tahir, 

    Kindly, we will not update to version 16.2.2 of the theme, as this version intoduces the bug we are experiencing (see original ticket for details).

    To reiterate, I've attached two images indicating the differences in display when we update the plugin to Salient v. 16.2.2. We do not want to display the additonal information that CANNOT be removed regardless of the configuration modifications we perform in the backend.

    Attached files:  salient16113-GOOD.png
      salient1622-BAD.png

  •  2,788
    Andrew replied

    Hi there,

    Thank you for getting back to us.

    Could you please create a staging site and update the theme to the latest version so we can check this out?

    To assist you better, we'd love to have a closer look at your setup and to do this, we'll need admin login credentials (dashboard URL, username, password) to your staging site. This will enable us to conduct a more in-depth investigation of the issue based on your specific configurations. Would you mind sharing this with us? 

    If you prefer, you can safely share the access through a one-time secret note or using an access plugin such as Controlled Admin Access.

    Before you provide this information, we strongly recommend taking a backup of your site.

    If you have any concerns or questions about this process, please don't hesitate to let me know.

    We look forward to your reply.

    Thanks,

  • purchasing416 replied

    We have created a staging environement at https://behaviour.2.webint.ca

    your administrator access credentials:

    username: salient

    password: 9QyU$HjEOnNSHNR*fTKfNjWI


    You will be prompted with HTTP Authentication:

    username: client

    password: client123

  •  2,788
    Andrew replied

    Hi again,

    Thank you for getting back to us.

    Could you please update the theme on the staging site so we can check this out and advise?

    We look forward to your reply.

    Thanks,

  •  2,788
    Andrew replied

    Hi again,

    Thank you for getting back to us.

    Have you tried using global sections for your blog posts? You can achieve this by setting the display location to Blog Archive Loop https://themenectar.com/docs/salient/page-builder-global-sections/.

    Try this and let us know how it goes.

    Kind regards,

  • purchasing416 replied

    We've updated the theme on the provided staging site. you are free to do what you wish with it. It serves only yu and will be destroyed when you are done with it.

    Modifying the way the Blog Post Archives is displayed could be a work around. The issue we would like addressed is why are the configurations being ignored since we updated the Theme.

  •  8,527
    Tahir replied

    Hey Again,

    Escalating this to the developer for further response. 

    Thanks.


    ThemeNectar Support Team 

  •  1,015
    ThemeNectar replied

    Hey purchasing416,

    It looks like your site is attempting to load the blog stylesheet from a non-standard location, which is causing the display issues:

    8583984387.png

    https://behaviour.2.webint.ca/wp-content/themes/salient/css/build/blog/nectar-blog-masonry-core.min.css (404)

    The file path which Salient should be using by default is: https://behaviour.2.webint.ca/wp-content/themes/salient/css/build/blog/masonry-core.css

    Could you enable the default WP file editor on your staging site so that I can take a look at the enqueue function within your instance to see why that path is wrong?

    Kind regards