Notifications
Clear all

[Solved] Page loads for Infinity after post

6 Posts
2 Users
2 Reactions
153 Views
Posts: 4
Topic starter
(@knavic)
Active Member
Joined: 1 month ago

For some odd reason after posting a topic, the page will load forever. Can anyone help? I turned off all the caching I could and problem still persists. https://inhelm.com/social/      Thank you

5 Replies
Posts: 4
Topic starter
(@knavic)
Active Member
Joined: 1 month ago

ad block recommended if visiting site 

Reply
4 Replies
Sofy
 Sofy
Admin
(@sofy)
Joined: 7 years ago

Support Team
Posts: 4573

@knavic 

Please check for any console errors. You can do this by pressing F12 to open the developer tools, then, navigate to the console tab. After clicking the 'Add topic' button, any errors will be displayed there.

Reply
(@knavic)
Joined: 1 month ago

Active Member
Posts: 4

@sofy     after I let it load for a very long time it went to a 503 screen and in console it said 

Uncaught (in promise) TypeError: Cannot read properties of null (reading 'debug')
at content-scope-messaging.js:32:29Understand this error

 

When I click content-scope-messaging.js 

const allowedMessages = [
    'getClickToLoadState',
    'getYouTubeVideoDetails',
    'openShareFeedbackPage',
    'addDebugFlag',
    'setYoutubePreviewsEnabled',
    'unblockClickToLoadContent',
    'updateYouTubeCTLAddedFlag',
    'updateFacebookCTLBreakageFlags'
]

function getSecret () {
    return new Promise(resolve => {
        window.addEventListener('ddg-secret', event => {
            event.stopImmediatePropagation()
            resolve(event.detail)
        }, { once: true })
    })
}

async function init () {
    const secretPromise = getSecret()

    // send off a message to the background to get config for this frame
    chrome.runtime.sendMessage({
        messageType: 'registeredContentScript',
        options: {
            documentUrl: window.location.href
        }
    }, async (argumentsObject) => {
        // Setup debugging messages if necessary.
        if (argumentsObject.debug) {
            window.addEventListener('message', message => {
                if (message.data.action && message.data.message) {
                    chrome.runtime.sendMessage({
                        messageType: 'debuggerMessage',
                        options: message.data
                    })
                }
            })
        }

        // if we didn't get the secret yet, wait for it
        const secret = await secretPromise
        // Init the content-scope-scripts with the argumentsObject.
        window.dispatchEvent(new CustomEvent(secret, {
            detail: {
                type: 'register',
                argumentsObject
            }
        }))
    })

    const secret = await secretPromise

    // Content-scope-script messaging proxy, to allow the Click to Load content
    // script to send messages to the extension's background and receive a
    // response.
    // Note: This event listener is only for Chrome MV3 builds of the extension,
    //       the equivalent Chrome MV2 event listener lives in
    //       content-scope-scripts/inject/chrome.js.
    window.addEventListener('sendMessageProxy' + secret, event => {
        event.stopImmediatePropagation()

        if (!(event instanceof CustomEvent) || !event?.detail) {
            return console.warn('no details in sendMessage proxy', event)
        }

        const messageType = event.detail?.messageType
        if (!allowedMessages.includes(messageType)) {
            return console.warn('Ignoring invalid sendMessage messageType', messageType)
        }

        chrome.runtime.sendMessage(event.detail, response => {
            const message = {
                type: 'update',
                messageType: 'response',
                responseMessageType: messageType,
                response
            }

            window.dispatchEvent(new CustomEvent(secret, {
                detail: message
            }))
        })
    })

    chrome.runtime.onMessage.addListener((message) => {
        window.dispatchEvent(new CustomEvent(secret, {
            detail: message
        }))
    })
}

init()

 

Sorry I don't know what any of this mean or if it's helpful.

Reply
Sofy
 Sofy
Admin
(@sofy)
Joined: 7 years ago

Support Team
Posts: 4573

@knavic

Please deactivate all plugins and switch to a default theme. Check if the issue is resolved. If it is, reactivate the plugins and theme one by one, checking after each activation to find the problem maker.

Reply
(@knavic)
Joined: 1 month ago

Active Member
Posts: 4

@sofy Thanks!! After doing this WP Mail SMTP turned out being the culprit. I went into the "misc settings" of the plugin and untoggled every option but "Allow Usage Tracking" and "Optimize Email Sending" works fine now! Thanks for the help, I was going nuts!

Reply