Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Amir

    (@amirfallah)

    Hello,
    From our investigation, we could not find any conflict between WP-Statistics and UiPress. We suggest that you please check the PHP error logs and also look for any errors in the Browser Console. This may provide more information about the issue causing the white screen on the WP-Statistics page.
    If you continue facing the problem after checking the logs, please feel free to share the error details or any additional information that could help us further troubleshoot the issue.

    Thread Starter WebCodePoet

    (@senjoralfonso)

    Hey, I have done a new installation of WP, than installed UIPress Lite and WP Statistics. The behaviour is the same.

    Console says: sm/f07d8d7b2652873f485707eab4f3d300bf1f6f3b42912e189c8933b1b9b3dfde.map missing, debug.log is empty.

    Plugin Support Amir

    (@amirfallah)

    Hi,

    I apologize for the delay in responding.

    Please enable the following three options in the wp-config.php file and then check for any displayed errors:

    define(‘WP_DEBUG’, true);
    define(‘WP_DEBUG_DISPLAY’, true);
    define(‘WP_DEBUG_LOG’, true);

    Additionally, if you are using an ad blocker, please disable it and check whether the issue is resolved or not.

    Providing further information and screenshots would help us better understand the problem and find a solution.

    Regards,

    Thread Starter WebCodePoet

    (@senjoralfonso)

    The only thing I get is this, seems not to be helpful ??

    [Error] Warning: ReactDOM.render is no longer supported in React 18. Use createRoot instead. Until you switch to the new API, your app will behave as if it's running React 17. Learn more: https://reactjs.org/link/switch-to-createroot
    	printWarning (react-dom.js:73)
    	error (react-dom.js:47)
    	render (react-dom.js:29680)
    	(anonyme Funktion) (index.js:1:54058)
    	(anonyme Funktion) (index.js:1:64980)
    	Globaler Code (index.js:1:64984)
    
    Plugin Support Amir

    (@amirfallah)

    Hi,

    We tried once again to replicate the issue with the aforementioned plugin, but we didn’t encounter such a problem. Unfortunately, the provided data wasn’t helpful either. I suggest continuing to contact the support team of the plugin responsible for causing this issue.

    Please ask us if you have any further questions or need assistance.

    Regards,

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Conflict with other plugin’ is closed to new replies.