[CP-SupportKeymaster Post count: 1282]

1. Those fields appear when “I will attend ” is selected. Because they are useless for the guests who rsvp “Sorry, I will no be able to attend”. If they do not appear it means there’s a problem with your website. Please provide a link to your website so I can investigate further.

2. Like it’s mentioned in the plugin documentation and on the demo page sidebar, the form will look just like your theme, it takes the theme’s styles for better integration. On the demo we use the Twenty Fifteen theme (slightly modified, with different fonts and buttons).

3. It seems that there’s a problem on your website, like I mentioned at point 1. Please provide a link so I can check.

[CP-SupportKeymaster Post count: 1282]

Hi. Sorry for the belated response, support was on Easter holiday.

The images loaded in css are in the theme’s images folder, just like any other WordPress theme.
The .psd files are in the PSD-files folder.

[CP-SupportKeymaster Post count: 1282]

In the current version (2.5) the theme shop page template does not have a sidebar on the right side, only in the footer (like it shows in the demo https://craftedpixels.net/demo-wp/vintage-wedding-theme/shop/ )

In new theme version (2.6) we submitted to ThemeForest the shop page will have a right sidebar too. We expect the update to be approved within the next 24 hours and you will receive an email notification from Envato when it’s approved.

[CP-SupportKeymaster Post count: 1282]

This reply has been marked as private.

[CP-SupportKeymaster Post count: 1282]

Hi. Please find the answers below:

1. The 2.5 update was in August 2015 and until February 2016 we kept the old 2.4 version included for the existing customers, just in case they want to revert. It was a long transition period, but as of 12 February 2016 we stopped including the old version because it was a little confusing for the new clients.

If you want to revert to the old version, we can send it to you via email.

2. The albums in the gallery were never centered, but left aligned, even in the old version. If you want to center them, go to Theme Options > CSS Styles and add this:

.vintage-gallery {
	margin: 40px auto 0;
	max-width: 80%;
}

4. Thanks for the bug report, I’ll look into it and fix it for the next update.

[CP-SupportKeymaster Post count: 1282]

I have an answer. To display the whole text you will have to use quotes. I modified your widget from text=Download Brochure to text="Download Brochure" and now all text is displayed.

This is the first time a button with text on 2 lines is tested, so it seems that the line-height is wrong. It will have to be added in the css file. Add this: line-height: 28px;" to a.button.xlarge.

[CP-SupportKeymaster Post count: 1282]

Ok. I logged in and checked. I moved the text=Download text after size to see if it makes any difference, but it has not.

I tested your code
[button size=xlarge text=Download Brochure color=blue link=http://littledarlingsnursery.co.uk/wp-content/uploads/2016/03/Little-Darlings-Brochure.pdf]
on our local server and the whole text displays (including brochure). I also tested on our online server on the theme demo, and the text gets cut exactly like in your case, the text after space is ignored (is considered another shortcode attribute).

I’ll assign the issue to our developer (he’ll conduct further tests on our servers) and let you know as soon as I have an answer.

[CP-SupportKeymaster Post count: 1282]

All your text should be displayed (“brochure” should show on a new line because of insufficient space). Please double check the code. If there’s a problem with that please provide access credentials to dashboard so I can check the widget.

[CP-SupportKeymaster Post count: 1282]

Yes, indeed it’s a problem only on Firefox. Chrome, Edge and Internet Explorer display the button ok.

Like I previously mentioned, you can use a smaller size of the button, there’s enough space to display it correctly. Or you can change the font size in the css file for the xlarge button ( a.button.xlarge ) from 24px to 22px.

[CP-SupportKeymaster Post count: 1282]

You can use a smaller button size, for example “large” will display correctly.

[CP-SupportKeymaster Post count: 1282]

On my machine the widget button looks like in the attached screenshot.

Please tell me what operating system and what browser are you using so I can reproduce the exact environment of the issue.

Attachments:

You must be logged in to view attached files.

[CP-SupportKeymaster Post count: 1282]

Please provide a link to your website so I can take a look to the compiled css styles.

[CP-SupportKeymaster Post count: 1282]

Sorry for that, looks like the update was approved with the missing plugin. We re-submitted the update to ThemeForest and should be approved shortly.

[CP-SupportKeymaster Post count: 1282]

You’re welcome.

Yes, uploading and activating the child theme will not affect the modifications you have made to the main theme.

If you redo in the child theme the modifications you have previously made to the main theme, than it will not be necessary for you to follow the two steps that I mentioned in the previous post. After copying your modifications to the child theme, just install the new version of the main theme and you will automatically be prompted to install the shortcodes plugin (like depicted in the screenshots in the “Installing” section of the documentation). Just click the button to install the plugin and that’s it.

Yes, to safely modify the footer.php file, just copy the footer.php file to the child theme and modify it there.

[CP-SupportKeymaster Post count: 1282]

No, uploading the child theme will not erase the modifications done in the main theme. But I would recommend that if possible redo all the modifications in the child theme, so that you can update the main theme safely. The plugin uses css styles that were added in the new theme version, so an update is mandatory.

If that’s not feasible for you, follow these steps:

1. Manually install the CP Shortcodes plugin (you can find it in the theme in the “plugins” folder).
2. Add the necessary css styles in your child theme or in the main theme’s style.css file. The necessary css styles are these:

button,
a.button,
input[type='reset'],
input[type='button'],
input[type='submit'] {
    font-size: 0.9rem;
    line-height: 1.3rem;
    text-decoration: none;
    cursor: pointer;
    display: inline-block;
    font-family: 'Solomon Normal', sans-serif;
    border: 0;
    -webkit-transition: all 0.5s ease-in-out;
    -moz-transition: all 0.5s ease-in-out;
    -ms-transition: all 0.5s ease-in-out;
    -o-transition: all 0.5s ease-in-out;
    transition: all 0.5s ease-in-out;
    border-radius: 4px;
    box-shadow: 1px 1px 0 #7d7d7d;
    padding: 10px 16px 6px;
    color: #fff;
    margin-bottom: 20px;
}

/* =Buttons (Colors)
-------------------------------------------------------------- */

a.blue {
    background: #5ccbe8;
    color: #fff !important;
}

a.red {
    background: #f1494f;
    color: #fff;
}

a.orange {
    background: #ec6713;
    color: #fff;
}

a.yellow {
    background: #f0c133;
    color: #161300;
}

a.green {
    background: #1fb044;
    color: #fff;
}

a.olive {
    background: #9fbc7a;
    color: #161300;
}

a.purple {
    background: #c072c5;
    color: #fff;
}

a.pink {
    background: #f9a6af;
    color: #fff;
}

a.brick {
    background: #d2804e;
    color: #fff;
}

a.gold {
    background: #f9dd45;
    color: #161300;
}

a.brown {
    background: #844926;
    color: #fff;
}

a.silver {
    background: #c0c0c0;
    color: #444;
}

a.gray {
    background: #696969;
    color: #fff;
}

a.black {
    background: #222;
    color: #fff;
}

/* =Buttons (Sizes)
-------------------------------------------------------------- */
a.button.small  {
    font-size: 10px;
    padding: 3px 6px;
    text-transform: uppercase;
    letter-spacing: 1px;
}

a.button.medium {
    font-size: 16px;
    padding: 8px 16px;
}

a.button.large {
    font-size: 18px;
    padding: 10px 35px;
}

a.button.xlarge {
    font-size: 24px;
    padding: 12px 55px;
}

[Author]

Posts