Viewing 2 replies - 1 through 2 (of 2 total)
  • Anonymous User 14808221

    (@anonymized-14808221)

    You seem to have updated since an older (not a recent) version since those things you mention are around since maybe a year now.

    The error you see, on the other hand, is something I want to put my hands on for a long time.
    Please see this:
    https://www.ads-software.com/support/topic/class-wp-installer-php-issue/#post-10140818

    The problem we do not have the steps to replicate it and a fix is not safe if we do not know why it happens.

    Do you happen to have a backup of your website of before all these issues started to happen? (Fingers crossed).
    If so, please reach out in this forum after registering here for free.
    Please mention the thread here, and ask for my assistance.

    Typically, Types still will display it’s Custom Fields using the ShortCodes.
    Those ShortCodes are typically inserted in the Post Body of your Custom Posts or native WordPress Posts/Pages.
    Here is the DOC for that:
    https://wp-types.com/documentation/customizing-sites-using-php/functions/
    Each of those fields can either be displayed with the API or with Custom Code.
    Can you confirm that this is how it’s done on your site?

    Thread Starter asdrugan

    (@asdrugan)

    xxx

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Error update 2.2.22’ is closed to new replies.