[Steven Zahm]

@ Michelle

Generally, if the code in the QuickTip does not function, it is because of one of the following:

• The code snippet was not activated, it was saved only. Check to make sure you’ve activate the code snippet.
• The shortcode option initial_results='false' was not added to the shortcode.
• If the shortcode option was added and you added by copy pasting it. Delete the shortcode and manually type it in.
• There as an array in the copy/pasting of the code when making the new Code Snippet. Try recreating it.

Hope that helps, please let me know.

[Steven Zahm]

@ Tim

Well, I determined this is being caused by the theme and not a bug with Connections. The attached screenshot shows the file and the problem section. All the lines that begin with // … I added them. With those added, Connections works just fine.

What is happening is that they are enqueuing several core WordPress admin scripts. Scripts that WP loads by default on most admin pages. This is causing them to be loaded twice on the Connections pages which in turn causes the event which toggles the box from open to closed, and visa versa, to be fired twice, so it never toggles like it should.

You can test this. Go the an entry with the issue. Click the arrow once, just once. Now reload the page without doing anything else. You will see that it toggled. If it does not, do it again because it does not always save due to the event being fired twice.

Honestly, I really do not understand why they are doing what they are doing and why. To me, and with what I know about best practices for developing for WP that does not seem right. The theme dev may very well have a very good legitimate reason. But, what they need to do is make sure that code will only run on their admin pages and the pages that is needs to run so it does not break other plugins.

I hope that helps!

ps. Those // I added, I removed them so as not to break the theme.

Attachments:

You must be logged in to view attached files.

[Steven Zahm]

@ Tim

Can you double check that login info? I get invalid login errors.

[Steven Zahm]

@ Tim

Hmmm… to debug further, I’m going to need an admin login. Details can be posted here as a private reply.

[Steven Zahm]

@ Tim

Oh, ok, I took a look at the original screenshots again… I think I took down a rabbit hole, apologies.

My nest guess is that those fields are collapsed. What happens when you click the arrow on the right?

[Steven Zahm]

@ Tim

Did you check the screen option tab when added a new entry? The screen options are save by action so you can have different screen settings when adding an entry vs. screen option when editing an entry. Can you share a screenshot of both?

[Steven Zahm]

@ Tim

My first guess is that you might have inadvertently turned them off. Click the Screen Options tab in the upper right of the page and add a check to thos fields if they do not have a checkmark.

Hope that helps, let me know.

[Steven Zahm]

@ Maria

No problem, it happens :) Great to hear it’s working!

[Steven Zahm]

@ Maria

See this FAQ. Specifically the top section about removing the <code> and <pre> HTML tags from around the shortcode. After you do, the template will look like it should.

I highly suggest reading this QuickTip that covers a couple basics when working with shortcodes for any plugin, not just Connections.

Hope that helps!

[Steven Zahm]

@ Deanna

In this file there is a lot of CSS that are overriding the style of the template. Specifically, this CSS:

.vcard {
    text-align: center;
    font-family: ff-meta-serif-web-pro, serif;
    letter-spacing: 0;
    font-style: italic;
    font-size: 12px;
    margin-bottom: 3em
}

.vcard .adr a {
    padding-right: 10px;
    background: transparent url(http://pelotonlabsportland.com/wp-content/themes/peloton/images/glyphicons_242_google_maps.png) no-repeat right top
}

.vcard .adr:after {
    content: "\2022"
}

.vcard .tel:before {
    content: "\2022\00A0"
}

.vcard .org,.vcard .country-name,.vcard .postal-code,.vcard .region,.vcard .locality {
    display: none
}

.vcard a {
    text-decoration: none;
    color: #444
}

.vcard a:hover {
    text-decoration: underline
}

Removing this should fix up the template. Hope that helps!

[Author]

Posts