Turn On Social

It’s a feature request for the regular version, cloning fields would be very useful

We have pro.

I mean duplicate / clone that item so when adding lots of similar fields it’s quicker

Good analogy @zandercent!

In that case, a copy of that pin would be locked in your car, your house, your office and your briefcase. If any one of them were ever opened, this would reveal the pin providing access your bank.

Not only that, the person who finds the pin would also get access to all the other bank accounts you own – since a master key opens access to all your CloudFlare domains without exception.

• This reply was modified 8 years, 6 months ago by Turn On Social.

Fair enough.

Asking customers to put their global API key in plain text on multiple WP sites seems like a substantial security risk. Much better to isolate it in some way with domain specific API keys for example.

Just following good security principles.

It does although previously the plugin allowed configuration of settings without utilising an API key (on v3 the first screen presented forces the user to)

That’s the output from https://www.ads-software.com/plugins/php-compatibility-checker/ – it’s static code analysis. I’ll add you to their whitelist.

There’s good guidance here on the readme.txt files: https://www.ads-software.com/plugins/about/readme.txt

Most plugin developers include the link to github in the Description like this: https://en-gb.www.ads-software.com/plugins/inline-comments/

For sure, as the maintainer you should always understand the code you’re merging!

Yep that’s as simple as using the built in Swift Mailer functions

// Create the message
$message = Swift_Message::newInstance()

  // Give the message a subject
  ->setSubject('Your subject')

  // Set the From address with an associative array
  ->setFrom(array('[email protected]' => 'John Doe'))

  // Set the To addresses with an associative array
  ->setTo(array('[email protected]'))

  // Give it a body
  ->setBody('My <em>amazing</em> body', 'text/html')

  // And optionally an alternative body
  ->addPart('My amazing body in plain text', 'text/plain')
  ;

Full ref: https://swiftmailer.org/docs/messages.html

Found it, maybe just reorder this?

The file you need to modify is:
/wp-content/themes/invent/framework/functions/utility-functions.php

function mo_footer_content() {

        // Default footer text
        $site_link = '<a class="site-link" href="' . home_url() . '" title="' . esc_attr(get_bloginfo('name')) . '" rel="home"><span>' . get_bloginfo('name') . '</span></a>';
        $wp_link = '<a class="wp-link" href="https://www.ads-software.com" title="' . esc_attr__('Powered by WordPress', 'mo_theme') . '"><span>' . __('WordPress', 'mo_theme') . '</span></a>';

        $my_theme = wp_get_theme();
        $theme_link = '<a class="theme-link" href="' . esc_url($my_theme->ThemeURI) . '" title="' . esc_attr($my_theme->Name) . '"><span>' . esc_attr($my_theme->Name) . '</span></a>';

        $footer_text = __('Copyright © ', 'mo_theme') . date(__('Y', 'mo_theme')) . ' ' . $site_link . __('. Powered by ', 'mo_theme') . $wp_link . __(' and ', 'mo_theme') . $theme_link;
        $footer_text = '<div id="footer-bottom-text">' . mo_get_theme_option('mo_footer_insert', $footer_text) . '</div>';
        echo do_shortcode($footer_text);
    }

The CSV should be comma separated, not semi-colon

Done

This is still broken

@media only screen and (max-width: 992px)
becomes
@media only screen and max-width 992px

Please fix W3TC

ref: https://sourceforge.net/p/csstidy/bugs/27/

Yes that’s correct! I’ve added a test string in both stable and dev and the stable copied over – so guess that’s the way to go

WordPress v4.3 changed the header tag that the plugin uses to show the error message, see here for temp fix:
https://www.ads-software.com/support/topic/wp-43-bug