509tyler

I corrected this issue on my site by adding this to my wp-config.php file:

`/** fix admin issues with jQuery**/
define(‘CONCATENATE_SCRIPTS’, false );

This worked for me setting additional nginx directives:
proxy_buffer_size 128k;
proxy_buffers 4 256k;
proxy_busy_buffers_size 256k;

CentOS Linux 7.4.1708 (Core)?
Plesk Onyx Version 17.5.3
PHP 7.0.25
FPM application served by Apache

https://www.howtoforge.com/nginx-upstream-sent-too-big-header-while-reading-response-header-from-upstream

Also Google: nginx upstream sent too big header while reading response header from upstream

You can set a constant in your wp-config file if you do not want the password stored in the DB like this:

define('WPMS_SMTP_PASS', 'your_password_goes_here'); // SMTP authentication password, only used if WPMS_SMTP_AUTH is true

See this article:
https://www.dangtrinh.com/2015/10/smtp-emailing-for-wordpress-multisite.html

@natalieneumann
plugins/shortcodes-ultimate/inc/core/shortcodes.php

The plugin has been updated since this post but again on line 974 I think it would be preferential to use https://maps.google.com/maps?q=

Great. Shall I wait for the new plugin update OR hack your plugin with this change? I don’t see file name or line numbers for this code change. I’ll post a followup with my testing results with the new code.

Yes. There is more than one plugin using Twig. Does WP intend to integrate Twig into core libraries I wonder?

You can change line 27 mentioned above from:
<span class="wu-day-current-temp">{{ day.temperature | round }}<sup>°</sup></span>

to:
<span class="wu-day-current-temp">{{ day.temperature | number_format }}<sup>°</sup></span>

And the twig template will no longer throw an error. You can read more about number formats for Twig here:
https://twig.sensiolabs.org/doc/filters/number_format.html

I am experiencing the same issue. If you are using current for the forecast, the rounding decimal value is not working. If you open up the folder called “templates” then open the file called “current.html” and edit line 27 and remove “|round” this will fix the template error.

From this:
<span class="wu-day-current-temp">{{ day.temperature | round }}<sup>&deg;</sup></span>

To this:
<span class="wu-day-current-temp">{{ day.temperature }}<sup>&deg;</sup></span>

I am looking for the real solution for rounding the temperature values correctly using Twig.

I found this article to be quite useful:
https://premium.wpmudev.org/blog/wordpress-email-settings/

I created a “plugin” in the mu-plugins folder so that the emails coming from the Events Manager would be something other than ‘WordPress” and then made the email from “Site Notifications – DO NOT REPLY” so that the end user will know not to reply to the email but click a link within the email they receive.

This works for me now – not ideal, but WAY better than coming from “WordPress”

That would be perfect!

Sorry. My fault on this. I think I have it sorted out. It was an error (naturally) on my end.

The path to the lightbox CSS and JS files are broken in the plugin code. I was forced to just comment out the code that called the css and js on lines 28-43 of facebook-photos.php since my theme has it’s own “lightbox” effect.

I then modified the plugin code on line 114 to add my own class to the output and this worked great. Hope this helps you and anyone else who might want to use this plugin – which works pretty well for my purposes.

It would also be great if the plugin author could limit the loading of css and js to just the pages that display the facebook galleries – this could be an option in the plugin settings.

Actually you can just modify lines 170-172 of /components/widget-beer-list.php like this:

$args = array (
		'post_type' => 'embm_beer', 'orderby'=> 'title', 'order' => 'ASC'
	);

It would still be great to have this as a Widget Option

Visual Composer has their z-index set higher than Shortcodes Ultimate. You can modify the Shortcodes Ultimate assets/css/magnific-popup.css and change all the z-indexes higher. I simply changed them from from 1042 to 1142. This corrects the problem. You might be able to add these styles to your theme’s css. This is kind of a hack, but if Vladimir simply changed the z-indexes of that file in his plugin then it would work with Visual Composer.

You could also modify the z-index of the Visual Composer CSS files … assets/lib/bootstap_modals/css/bootstrap.modals.css file to lower the z-index of their modal to less Line 43 to:
z-index: 1010;
and Line 58 to:
z-index: 1020;

Either solution corrects the modal conflict with Shortcodes Ultimate and Visual Composer.

I am experiencing the same issue. It is a z-index issue. The VC z-index is 1059 and the Short Codes Ultimate modal window open behind the VC modal window. I am able to hack the z-index with Fire Bug but it sure would be great if these 2 plugins played nicely together!