Home Forums Landing Pages [Landing Pages] Fatal Error Activating Inbound Pro

This topic contains 1 reply, has 2 voices, and was last updated by  Hudson Atwell 2 weeks, 1 day ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #132034

    FutureLifeScience
    Participant

    Downloaded the Free Pro Version of Landing Pages -> Inbound pro.
    Fatal Error On Activation.
    Have tried different Themes
    Have disabled all Plugins bar SSL
    No Luck Does Not work at all

    Standard Landing Pages Version.. Cannot get into Settings. Error 500
    Other than a separate plugin to remove the subfolder /go/ have you got an option to remove this?
    Reason: Using Multi Domain Redirect it does not like subfolders.

    Ideally I would also like to add a way for a client account to edit the Landing Page – FRONT-END.
    I never want to make any client see the back end because they panic.. Its too complicated for most..
    A simple MyAccount page with the ONLY few options they need.
    Eg.. Tried User-FrontEND.. To edit posts. Perfect. But very limited.
    Could we use the Landing Page edit with User FRONT END?

    Did check your forums for answers for Fatal Errors.. There are many. Just no reply in anyone of them.

    Cheers

    Ivan

    #132035

    Hudson Atwell
    Keymaster

    “Downloaded the Free Pro Version of Landing Pages -> Inbound pro.
    Fatal Error On Activation.”

    Will you try enabling WP_DEBUG to see if you can find out what the fatal error message is?

    http://codex.wordpress.org/WP_DEBUG

    “Ideally I would also like to add a way for a client account to edit the Landing Page – FRONT-END.”

    We do have a front end editor for landing pages. It’s called ‘Visual Editor’. The button to launch should look like this:
    https://www.screencast.com/t/bVPjMokZzx
    https://www.screencast.com/t/YRVqPdbn

    “Other than a separate plugin to remove the subfolder /go/ have you got an option to remove this?”

    No unfortunately not. But in the settings area you can change /go/ to something unique.

    Hope this helps move the troubleshooting process forward,
    Hudson Atwell

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.