Hello,
I have identified an issue in the EventON 5.1 release package that causes a 403 error in the WordPress admin area when PHP execution protection is enabled for the /wp-content/plugins/ directory.
While editing an EventON event, EventON attempts to load the following stylesheet:
/wp-content/plugins/eventON/assets/css/jquery-ui.min.css?ver=5.1
However, this file does not exist at that location in the EventON 5.1 package.
The actual file is located at:
/wp-content/plugins/eventON/assets/css/lib/jquery-ui.min.css
As a result, the request to the incorrect path eventually results in a request to:
/wp-content/plugins/eventON/assets/css/index.php
which is blocked with a 403 Forbidden response by WPMU DEV Defender when the "Prevent PHP Execution" security feature is enabled.
I compared the installed plugin with a clean copy of the original EventON 5.1 distribution, and the incorrect asset path appears to originate from EventON itself rather than from a local modification.
The relevant enqueue should therefore point to:
AJDE_EVCAL_URL . '/assets/css/lib/jquery-ui.min.css'
instead of:
AJDE_EVCAL_URL . '/assets/css/jquery-ui.min.css'
Could you please check and correct this asset path in the next release?
I also noticed a separate packaging/cleanup issue in the EventON 5.1 distribution.
The production ZIP contains macOS-generated metadata/artifact files and directories, including:
.DS_Store
__MACOSX
These files are not required by the WordPress plugin and appear to have been unintentionally included when the release archive was created. It would be advisable to exclude .DS_Store, __MACOSX, and similar development/OS metadata from production release packages.
To summarize, the two issues I found in the EventON 5.1 package are:
1. Incorrect admin jQuery UI stylesheet path
Requested:
/assets/css/jquery-ui.min.css
Actual file:
/assets/css/lib/jquery-ui.min.css
2. Release package cleanup
The production ZIP contains unnecessary macOS artifacts such as:
.DS_Store
__MACOSX
I can provide the browser Network/Initiator trace and the original EventON 5.1 package used for comparison if needed.
Thank you.
- Oct 7,2026 AT 11:19AM - 2 hours agoHello,
Could you also send us a screenshot of the error, if possible?
I am also going to escalate this ticket to development to help in here. Please allow us some time to address this, and we truly appreciate your patience. Thank you for being a valued EventON customer!
Thank you for letting us know we will get this resolved in the next version update!