Title: Internal server error &#8211; Widget shortcode and Yoast
Last modified: August 22, 2018

---

# Internal server error – Widget shortcode and Yoast

 *  [roydekker](https://wordpress.org/support/users/roydekker/)
 * (@roydekker)
 * [7 years, 9 months ago](https://wordpress.org/support/topic/internal-server-error-widget-shortcode-and-yoast/)
 * Hi all,
 * Today we have installed a clean wordpress installation. We using the latest version
   of WordPress and the Yoast plugin. But after activating the shortcode plug-in
   we get an internal server error on the front-end of the website.
 * After some tests it seems this plugin doesn’t work well with yoast SEO.
 * How to solve this?

Viewing 1 replies (of 1 total)

 *  Plugin Author [shazdeh](https://wordpress.org/support/users/shazdeh/)
 * (@shazdeh)
 * [7 years, 9 months ago](https://wordpress.org/support/topic/internal-server-error-widget-shortcode-and-yoast/#post-10623290)
 * Hi!
    I have both plugins but do not have any errors. Can you please enable debugging
   in WP (see: [https://codex.wordpress.org/Debugging_in_WordPress](https://codex.wordpress.org/Debugging_in_WordPress))
   and see what is the error message by checking the error log files?

Viewing 1 replies (of 1 total)

The topic ‘Internal server error – Widget shortcode and Yoast’ is closed to new 
replies.

 * ![](https://s.w.org/plugins/geopattern-icon/widget-shortcode.svg)
 * [Widget Shortcode](https://wordpress.org/plugins/widget-shortcode/)
 * [Support Threads](https://wordpress.org/support/plugin/widget-shortcode/)
 * [Active Topics](https://wordpress.org/support/plugin/widget-shortcode/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/widget-shortcode/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/widget-shortcode/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [shazdeh](https://wordpress.org/support/users/shazdeh/)
 * Last activity: [7 years, 9 months ago](https://wordpress.org/support/topic/internal-server-error-widget-shortcode-and-yoast/#post-10623290)
 * Status: not resolved