WolfieZero

Cheers for having a look; not to say it was your plugin per-say but always worth letting people know just-in-case.

Annoyingly I did delete the files causing it straight off the server but the server company did get the headers of the email it was sending out.

Received: (qmail 22305 invoked from network); 7 Mar 2015 13:15:31 -0000
Received: from unknown (127.0.0.1)
   by 0 with QMQP; 7 Mar 2015 13:15:31 -0000
To: [email protected]
Subject: Wyrwij sie z finansowej niewoli i badz niezalezny
X-PHP-Originating-Script: 20760:.include.php(1498) : eval()'d code
Date: Sat, 07 Mar 2015 13:15:31 +0000
From: Piotr Szymanski <support@THE_DOMAIN.com>
Message-ID: <9a7b6b4f2d29495014bc96083ca2df12@THE_DOMAIN.com>
X-Priority: 3
X-Mailer: PHPMailer 5.2.9 (https://github.com/PHPMailer/PHPMailer/)
MIME-Version: 1.0
Content-Type: multipart/alternative;
  boundary="b1_9a7b6b4f2d29495014bc96083ca2df12"
Content-Transfer-Encoding: 8bit
X-Host-Domain: THE_DOMAIN.com
X-Host-Script:
/domains/b/a/THE_DOMAIN.com/public_html/wp-content/plugins/better-search-replace/templates/.include.php
X-Host-Server: ...
X-Host-Client: ...

(Blanked out sensitive data)

I’m doing an audit of the site now but if you’re happy it’s nothing to do with your plugin then I’m happy with that as well. Thanks for having a look though!

Ah fair enough. I’ll look and see about helping with that bit of code then, luckily it’s only a notice so nothing serious.

Thanks for the help! ??

Yeah, it’s for ease of multiple environments. I’m working on multiple dev environments and a staging one so there are different URLs for each. Bit of an odd setup for WordPress I know but makes my life that bit easier ??

Thanks.

I’m removing the domain manually via the editor or just doing a search and replace in the DB on the post_content field. Also I’ve updated Jetpack to 2.9 now and it still happens ??

+1 for adding support natively. Not sure I’m a big fan of editing plugins as it will probably get overwritten when somebody else updates the plugin.

Might be a bit delayed but least I have an answer…

Use single_post_title() and apply the hook to that as it will only affect the current post title rather than all.

Seems to be fine in Chrome (where I tested it originally), should be fine in Opera when I use Dragonfly, so might be a cache issue. Are you still editing the CSS file as the value keeps changing in Opera?

Hi ChorleyPS,

if you go into the simply-poll plugin folder and go to /view/client/simply-poll.css. Look for the class .sp-label you should see the following

.sp-label {
	display:	inline-block;
	width:		210px;
}

change that width value from 210px to auto and that will fix your issue.

Might be worth noting that you can make any style changes you want to Simply Poll in this file.

Hope that helps!

Hi,

Yeah, this is a known issue; I’ve been given a fix to solv it but I’ve not been able to implement it yet. I’ll update this post when I do, but it should be some point next week if I get the chance.

Thanks!

Thanks for that wollernic, I’ll change that in the next version. ??

Hmm, I’m struggling to understand what is causing this error, but by the looks of it the config.php file in the Simply Poll folder isn’t being called as the capitalised words are global constants that are defined in said file.

Can I check that you’ve installed other plugins and they work, but also that you haven’t change anything with the WordPress install and/or the Simply Poll files.

Thanks.

Awesome! Nice simple fix too ??

Hope you enjoy the plugin and if you get any more issues or have any suggestions then feel free to contact me.

Ah, I think I know exactly what your issue is.

It seems as if the simplypoll.js file isn’t being loaded; this normally happens due to the theme not having the wp_footer() function (normally located in the footer.php file of your theme. If it’s not there then add it in just above the closing </body> tag.

Really, any WordPress theme requires this function to keep plugins working (as the best time to call Javascript is at the end of a page load)

Let me know if that works ??

Hi mczinger,

To best solve this you will need to go into your simply-poll plugin folder that can be found from the root of your WordPress install wp-content/plugins/simply-poll and edit a file called config.php.

On line 6 where it says define('SP_DEBUG', false); can you change the value false to true so it reads define('SP_DEBUG', true);.

Run the plugin a few times so you get the error message appear a few times. Then go back to the simply-poll folder and open the log file (with any text editor) and copy and paste the contents to the forum and I should be able to see where your issue possible occurred.

Thanks!

At the moment, it’s a bit of a mission to do it; you’ll need to understand MySQL and PHP in-order to grab the results. I can add this in as a suggestion to version 2 though.