hand_coding

Hi,
A small follow-up just in case people are still struggling with tracking pixel:
Tracking pixel won’t work if you put wp-config outside the root directory (into the root’s parent directory).
That’s unfortunate because this the safest place.
I hope the developer may address this issue in a future update.

Fabrice

The KNEWS_CUSTOM_SPEED constant definitely doesn’t work for me.
Any value defined here sets the default speed to 2 test mode in the admin.

However, I found the source of the tracking pixel problem thanks to your last post:
“simply define it on wp-config.php on root”, you wrote. “on root”.
Wordpress installation allows, and even recommends, that we put the wp-config.php OUTSIDE the root folder. Into the root’s parent folder if we have permissions to do so.
I do that because it’s far more secure and anybody being allowed to do so should.
Bringing the wp-config back to the www folder bring back the kitten but I won’t do it.
I’d rather keep the wp-config at the top level.
Do you think you can change that?

Regards,
Fabrice

Subscribe form before

After ‘send’ is clicked

Hi Carles,
The can't readand unsubscribe problems are solved since it was my fault (I messed up with the % shortcode).
As for the tracking pixel issue, it worked once, but now it’s gone.
I guess an htaccess rule prevents it to work properly.
I’m reluctant to work on it right now know because the website is in production.

1) What I’d like now, is to get a valid KNEWS_CUSTOM_SPEED constant.
But when I define it, it’s just ignored.
2) As I wrote earlier, the subscribe form on your website is totally broken for me.
It’s a shame for a website dedicated to a newsletter plugin and a bad signal for customers.

Thanks for your time,
Fabrice

When I say ‘Thanks’ I mean it.
Thank you for your time.

Fabrice

Hi again,
I didn’t noticed there was an update until you mentioned it (?)
I just updated now, removed the silly wp-conf but still no luck with tracking pixel.
Frankly, I’m not willing to put much effort with this plugin.
At least it works for the most part and I’m very doubtful it is reliable at this point.
1) No kitten.
2) No change log for 1.7.7 update.
3) Stupid forgotten php file.
4) The first custom constant I tried to configure (following the examples here is just totally ignored.
5) Did you try the ‘subscribe’ form on their website? Lot-of-fun experience for me (tested with Firefox 40 and Safari 8 on Mac).

Thanks,
Fabrice

Hi,
Thank you for your help.
Actually I found your post shortly after I posted this.
Removing the forgotten wp-config file did solved the problem.

Ironically, now it’s broken again for me.
No idea on what’s happening.

Thank you anyway…
Fabrice

Ah. Sorry, I thought you found a way to list your posts with a custom field in the admin panel.

I used the filter on the_title to replace the title with something appropriate

How do you do that?

Well that was rather simple actually.
The modifications bellow allows for writing and reading string data in place of serialized array if the array contains only one child (dropdown)

mf_post.php, line 278:

// Adding field value meta data
add_post_meta($post_id, "{$field_name}", $value);

becomes:

// Adding field value meta data
if(is_array($value) && count($value) == 1){
  add_post_meta($post_id, "{$field_name}", implode('',$value));
}else{
  add_post_meta($post_id, "{$field_name}", $value);
}

mf_front_end.php, line 481:

case 'dropdown':
  $result = ($options['multiple'])? $value[0] : $value ;
  break;

becomes:

case 'dropdown':
$result = ($options['multiple'] == '0' && is_array($value))? $value[0] : $value ;
break;

This doesn’t break previously entered data and update new/modified to the new format.

Fabrice

Oh… Ok.
I tried it but how do you spot your CPs in the admin panel (without title, that is)?

Yep. WordPress doesn’t allows you to ditch the title. This info is needed to construct the slug, view your posts in list, as well as retrieving the post by name or title; you have to keep it and I’d suggest you find a good use for it.
However, the editor can be disabled.

And what did you do to try to find the cause of the problem?
Please provide at least some details on your setup.
The only thing I know so far, is that a function in my code was preventing the correct execution of the ajax part of the wysija plugin.

As ideas comes out: do you use any ajax plugin?

Also, if your theme structure allows it, make a test with a default theme (like TwentyTwelve).