warfare-plugins / social-warfare Goto Github PK

When the horizontal buttons are present on the same page as the vertical ones, the plugin uses the left edge of the horizontal buttons to determine whether or not there exists enough space to display the floating sidebar buttons. On pages where the horizontal buttons are not present, the plugin displays the sidebar no matter the size of the screen because it does not know where the left side of the content area ends or how much space is available in the left margin. This causes it to show up on all screen sizes, covering up the left edge of the content area on smaller screens.

Note: If you have any additional information or insight on this issue or any questions, please share in the comments below!

When Social Warfare is activated, CSS Hero will load, but not run. It shows up, but it doesn't perform any of its functions.

Notes from a Customer: I'd love to utilize Social Warfare in a widget area and know I can do so using the shortcode. [social_warfare]. However, that renders my standard button set in relatively small area. Too small to show counts. I was wondering if there is an easy way that I could tell it to just show the Facebook and Google buttons in that particular area, like using options with the shortcode. [social_warfare id="FG" size="large"] for instance would show only the Facebook and Google buttons using the large button variant like the right oriented floating bar.

Note: If you have additional input on this idea, please add it in the comments section below.

Depending on how certain themes populate the snippets or "excerpt" for blog posts, sometimes the share button words and share counts are showing up at the beginning of the excerpt.

Some users want the ability to connect their social accounts to the plugin and have new articles automatically posted when they are published.

If this a feature you are interested in, please comment below expressing your support.

Fatal error: Cannot unset string offsets in /home/admin/public_html/blog/wp-content/plugins/social-warfare/functions/admin-page-class/admin-page-class.php on line 2274

Our shortcode generator is using the old [socialWarfare] shortcode as opposed to the udated [social_warfare] version.

Twitter recently removed the ability to query share counts from their services. We are currently working with Open Share Count (http://www.opensharecount.com) to remedy this.

Notes from User: "I ran another test, installing the plugin on a very basic multisite install -- same thing happens ... Super Admin can see the nav menu item and access settings, regular Admin user on an individual site that the plugin is enable for cannot."

We are tracking an issue on a small percentage of installs where the registration function is failing.

In most cases, if experiencing the infinite loop (where the page is trying to register but never stops) the following troubleshooting steps will fix the issue:

1. When the loading page appears, click the X button that tells the browser to stop loading the page.
2. Right-click anywhere on the screen and select "Inspect Element"
3. Locate the body tag and by double clicking on the list of class names, remove the sw_loading class.
4. Click on the Registration tab of the Social Warfare options page.
5. Click on "Deactivate" at the bottom of the page.
6. Enter your email address and click "Activate"

However, there are a rare number of cases where this still does not solve the problem. We are currently working on finding a solution.

Neither myself or anyone on my team has been able to replicate this bug on any of our devices. If anyone has additional information that might help us identify the cause and solve this issue, please let us know.

The horizontal buttons do not get generated from manual placements, but only from the automatically placed ones.

The cache rebuild is a background process. It is triggered by javascript calling the URL of the post being viewed with a specific URL parameter attached to it which instructs the server to run the API calls. It looks like this:

http://domain.com/the-blog-post/?sw_cache=rebuild

However, when the permalink contains a question mark, it adds another one breaking the way that URL parameters work. IT looks like this:

http://domain.com/the-blog-post/?something=something?sw_cache=rebuild

But it should look like this instead:

http://domain.com/the-blog-post/?something=something&sw_cache=rebuild

Allow for placement of Click-to-Tweets that will tweet a link to a page different than the one it was placed on. (Similar to the ability to add share buttons for a designated post_ID).

• Create an option for selecting the visual styles
• Output the classes from the selected visual style
• Add the necessary CSS for each style

Since we now hide all zeroes regardless of the option, this option is no longer needed and should be removed.

If you load a page on a mobile device (ex. iPhone) the buttons display fine.. If you move to landscape (turn phone sideways) the buttons expand to and show numbers. However, if you then switch back to portrait, some of the buttons will not switch back and you end up with two lines.

The icon sizing algorithm used to check for the presence of a border on the buttons by checking for a border-identifying class that we would add to the buttons. During our last CSS rebuild, we added borders to all buttons for consistency. Of course, the buttons that shouldn't visually have a border simply get their border color set to match the button color.

However, this means that all buttons always have borders and that algorithm needs to stop checking for borders and simply always assume the extra 1px on the left and 1px on the right of space needed to properly size the buttons.

This should solve the rare instances where the buttons size themselves in such a way as to push the last button onto a second line.

The bottom floating buttons require at least one iteration of the static horizontal buttons. This is because we have no idea how wide your content area is, so we literally create the regular set and then clone that set to the bottom.

However, some users would like to be able to turn on the floating buttons without having the static buttons on the page. We currently have this setup to work for the left floating buttons. Now I need to make it work for the top and bottom floating buttons as well.

http://simplepodcastpress.com/?ref=https://simplepodcastpress.com/?ref=98

The left floating sidebar buttons appear on all post types except on pages.

We are tracking some occurances where despite having the display settings configured properly, the buttons are not showing up on certain pages or post types.

When Social warfare is active the slide does not work, you see only a circle loader. When Social Warfare is disabled the slider works as it should.

We have had some people say that Social Warfare is not working with their Visual Editor plugin (or a visual editor built into their theme). We have solved a handful of these instances and currently we're only seeing issues with the Cornerstone Visual Editor.

If you have encountered any other conflicts with visual editors, please be sure to add them below.

PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, function 'social_warfare_deactivation' not found or invalid function name in D:...\wp-includes\plugin.php on line 503

1. Add options to options-page.php
2. Add output to header-meta-data.php

Many users are asking for a widgetized feature that allows them to showcase how many followers they have on each social network and that would also make it very easy for users to click those icons and follow them on the respective social networks.

Create a page and consolidate all of the social media identity fields into that options tab.

Some folks who don't get a lot of traffic aren't getting their cached counts reset very often. In some of these cases, they prefer to have the numbers regenerate and show the updates on the page load rather than being triggered after the page load.

Once every 24 hours we check if the registration is still valid. If the license is sitting on a different domain than the domain it was originally registered on, it will automatically attempt to update it's registration on the new domain.

This includes:

1. Changing from http to https (or vice versa)
2. Chanding from www to non-www (or vice versa)
3. Moving from one domain to another
4. Moving from a development domain to a different live domain

When parsing the response from our server, we were using the JSON decode function which was converting the information into a PHP object, but we were treating that information as if it was an array. This mismatch was throwing a fatal error and would kill the page from continuing to process.

I've now updated it so that the JSON decode function parses it into an array.

This was included in the 1.3.17 release on Monday, December 14, 2015.