I require support for a conflict with WP-discuz, which is conflicting with the activity settings> inside BuddyPress function. I have contacted buddypress and other developers, they have all said WPDiscuz should be rising this. Please can you take responsibility and help me resolve this issue. BuddyPress do not have the support to fix this and it can only be fixed from WPDiscuz's side!!
What will it take to fix this, do you want payment to correct the issue. Please confirm!!
If you can not fix this then I will have to find an alternative plugin instead of WPDiscuz and will like to request a full refund for the plugin and all of the WPDiscuz Addons please
I am using very powerful and intelligent error monitoring systems on my dedicated server and it detects the issue to be at /wp-content/plugins/wpdiscuz/utils/ajax/wpdiscuz-ajax.php.
E_WARNING: fclose() expects parameter 1 to be resource, bool given
in fclose called at
(287)in wp-content/plugins/wpdiscuz/utils/ajax/wpdiscuz-ajax.php (10)
| Error Type | Definition and Next Steps |
|---|---|
| E_ERROR | This is a fatal error that causes script termination. These are typically caused by calling a non-existing object like a class or function. This can often occur with version incompatibility. You should update your WordPress version, themes, and plugins. |
| E_WARNING | This is a run-time warning that does not cause script termination. These are potential issues that occur but do not stop the processing of PHP. These can often include deprecation warnings, which indicates that your code may be using an outdated version of PHP and needs to be updated. A warning in your PHP logs may not necessarily be related to the issue you are experiencing. |
| E_PARSE | This is a compile time parse error. This is usually indicative of a PHP syntax error, such as a missing semicolon ;, parenthesis (), opening or closing bracket {}, or any number of other syntax errors. You should review the file and line specified in the error message and look for potential syntax errors. |
| E_NOTICE | This is a run-time notice caused by an error in code. These are typically PHP errors that don't cause script termination. These errors indicate that there could be an issue with the code but may be normal functionality of the script. One common cause can be using a PHP variable that is undefined. A notice in your PHP logs may not necessarily be related to the issue you are experiencing. |
E_WARNING: fclose() expects parameter 1 to be resource, bool given
in fclose called at
This issue doesn't have any relation to the main issue you've mentioned.
I require support for a conflict with WP-discuz, which is conflicting with the activity settings> inside BuddyPress function. I have contacted buddypress and other developers, they have all said WPDiscuz should be rising this. Please can you take responsibility and help me resolve this issue. BuddyPress do not have the support to fix this and it can only be fixed from WPDiscuz's side!!
In this case, we've added new functions that will not allow the BuddyPress function works in the comment deleting process. However, we are not responsible if BuddyPress functions will not work properly in other places.
Wait for the next update the new changes will be implemented in the next version (no ETA).
@asti Can i hire your people to do this now. I cannot wait for too long. My developer is trying to find a solution but is worried that it will be removed every time WPDiscuz updates or changes its core structure
Hi, where can i download it to test. It is now showing as an available update. Also does this include the issue with the emoji not closing ?
@asti Hi Ashti, i was able to download directly via WP plugins update as you made it available as a global update. Please confirm if your teams were also able to resolve the issue with the Emojis add-on, not being able to auto close. Although this seems to be a minor issue but it could potentially affect users from using it. Many thanks 😉
Please confirm if your teams were also able to resolve the issue with the Emojis add-on, not being able to auto close.
The answer still the same as I've already mentioned here. the issue comes from the priority-nav.min.js file. It causes the issue.
