Title: PHP errors were triggered
Last modified: March 13, 2021

---

# PHP errors were triggered

 *  [herethereandhome](https://wordpress.org/support/users/herethereandhome/)
 * (@herethereandhome)
 * [5 years, 2 months ago](https://wordpress.org/support/topic/php-errors-were-triggered/)
 * Hi, Ive used the Easy Photogrphy Portfolio for a while and more recently (maybe
   after WordPress updates) when I try to add a new portfolio entry or edit old 
   ones this message appears and you can’t view any of the images the entry is just
   a blank portfolio page:
 * PHP errors were triggered during an Ajax request. See your browser developer 
   console for details.
 * I have tried uninstalling and reinstalling, removed the Yoast widget and made
   sure everything is updated. Forgive me if this is an obvious problem to solve
   but I’m fairly inexperienced at WordPress. I don’t want to stop using this portfolio
   but I can’t update it without this issue happening so am a bit stuck. Any help
   much appriciated at this point
 * Many thanks!

The topic ‘PHP errors were triggered’ is closed to new replies.

 * ![](https://ps.w.org/photography-portfolio/assets/icon-256x256.png?rev=1564371)
 * [Easy Photography Portfolio](https://wordpress.org/plugins/photography-portfolio/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/photography-portfolio/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/photography-portfolio/)
 * [Active Topics](https://wordpress.org/support/plugin/photography-portfolio/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/photography-portfolio/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/photography-portfolio/reviews/)

## Tags

 * [Easy Photography Portfolio](https://wordpress.org/support/topic-tag/easy-photography-portfolio/)

 * 0 replies
 * 1 participant
 * Last reply from: [herethereandhome](https://wordpress.org/support/users/herethereandhome/)
 * Last activity: [5 years, 2 months ago](https://wordpress.org/support/topic/php-errors-were-triggered/)
 * Status: not resolved