[Steven Zahm]

@ cheryl

Yes, the main site is fine… when you have a chance to get me the FTP login, I’ll fix the subfolder site you were letting me debug on.

[Steven Zahm]

@ R.Miles

Sounds like you have the Contact extension installed. With that installed and active the email address will not be displayed.

Which version of the Contact extension do you have? I just released an update yesterday, version 1.2, that fixed a bug which would cause email not to send. If you are experiencing this bug you would get a message stating; “You filled out a form field that was created to stop spammers. Please go back and try again or contact the site administrator if you feel this was in error.”

If nothing is happening at all… then the very likely issue is a javascript error in another plugin or theme. You can view any errors by opening the page in Chrome, hit the F12 key and clicking the Console tab. Are any errors being shown?

[Steven Zahm]

@ Lisa

Looks right, but have you tried it using the Code Snippets plugin like in the QuickTip? I’ve haven’t tried running this from the theme’s function.php… though that should work.

Also, I see you have the priority set as 10 instead of 1000. Have you tried setting it to 1000 as it is shown in the QuickTip?

[Steven Zahm]

@ Serge

You can use the solution in this FAQ to fix this.

Hope that helps.

[Steven Zahm]

@ cheryl

I just release version 2.0.1 which contains the fix.

[Steven Zahm]

@ cheryl

First, my apologies! I fat fingered a change in code when doing debugging and brought down the site. If you give me FTP access I’ll fix it immediately.

Sorry, but I am going to have to respectfully disagree with Shape 5. There are bugs in their theme causing the issue and I located the specific one causing the issue! What follows is a sampling of some of the bugs in the theme.

File:
/vertex/s5flex_menu/flexmenu.walker.php

Line 16 is this:
function start_lvl(&$output, $depth) {

Should be:
function start_lvl(&$output, $depth = 0, $args = array()) {

Line 25 is this:
function end_lvl(&$output, $depth) {

Should be:
function end_lvl(&$output, $depth = 0, $args = array()) {

Line 45 is this:
function start_el(&$output, $item, $depth, $args) {

Should be:
function start_el(&$output, $item, $depth = 0, $args = array(), $id = 0 ) {

Line 175 is:
function end_el(&$output, $item, $depth) {

Should be:
function end_el(&$output, $item, $depth = 0, $args = array()) {

Line 196 is:
function start_lvl(&$output) {$output = $output;}

Should be:
function start_lvl(&$output, $depth = 0, $args = array()) {$output = $output;}

Line 203 is this:
function end_lvl(&$output) {$output = $output;}

Should be:
function end_lvl(&$output, $depth = 0, $args = array()}

Line 213 is:
function start_el(&$output, $item, $depth, $args) {

Should be:
function start_el(&$output, $item, $depth = 0, $args = array(), $id = 0) {

None of the above is the cause. This is..

In the this file /vertex/includes/classes/standalone_functions.class.php on lines 196–198 is the following:

add_filter('the_content', 'do_shortcode', 11);
add_filter('widget_text', 'do_shortcode');
add_filter( 'gettext','do_shortcode');

The last line is a major error and I can not see any valid reason to add such a filter. As soon as that line is removed, everything works fine. The first line does not make any sense to me either as WordPress already filters for and runs the shortcode filter on the post content. Doing this could have unintended consequences for any other plugin which add their own shortcode and expects WordPress to handle the processing of shortcode in the correct order. On the flip side, this could be harmless with the only real negative is the increased overhead on each page load from running the shortcode parser on the post content multiple times.

Now, you might be asking why does that last line only affect Connections… The gettext function is a core WordPress feature (put simply) that allows text in WordPress, themes and plugins to be translated. At least one of the translatable strings in Connections has the [connections] shortcode in it as an instruction for the user. Adding the shortcode filter to the gettext makes WordPress run the shortcode and this is something that WordPress and Connections was not designed to handle to it was causing a fatal failure in ajax requests.

Another very real consequence of this filter is that every string in WordPress, theme and every plugin will be run thru the WordPress shortcode parser which will very likely have negative impacts on page load times.

[Steven Zahm]

@ Charlotte

Go to the Connections : Settings admin page, click the Display tab and change the Date Format to F j. That should do it. Hope that helps!

If you have a moment, I would truly appreciate a review as they really do make a difference. Many thanks in advance!

https://wordpress.org/support/view/plugin-reviews/connections

[Steven Zahm]

@ Gill

I actually released it yesterday.

[Steven Zahm]

@ cheryl

If you entered your support license key on the Connections : Settings admin page under the License tab, you’ll be notified in the admin of the update and will be able to update in the admin by clicking the update link. If you did not, then you will have download it from your purchase history.

As for the update, I plan on releasing it today as it should not take too long to migrate the fix to the three remaining widgets that require it.

[Steven Zahm]

@ cheryl

This was a little tricky to figure out a fix… it presented somewhat of a chicken and egg problem. Any way I have one of the widgets fixed with the solution that I came up with. Now all I have to do is make the same changes to the remaining widgets.

[Author]

Posts