swisspenelope

I love this plugin – and it’s the basis of the services provided by my best client, so I am a great fan. It’s also pretty easy to “tweak” because it’s so nicely structured.

Thanks!

Yes! Sorry – I totally forget to get back to you about this. In the class.swpm-form.php file, I changed my code to

protected function payment_amount()
  {
    $payment_amount = filter_input(INPUT_POST, 'payment_amount');
    if ($payment_amount < 0)
    {
	$this->errors['payment_amount'] = SwpmUtils::_('Invalid payment amount field');
	return;
    }
    $this->sanitized['payment_amount'] = $payment_amount;
  }

and in the views file, which in my case is called admin_member_edit_fields.php, I now have:

<tr>
  <th scope="row"><label for="payment_amount"><?php echo  SwpmUtils::_('Payment Amount') ?> </label></th>
  <td><input name="payment_amount" type="number" id="payment_amount" step="0.01" value="<?php echo esc_attr($payment_amount); ?>" /></td>
</tr>

Everything was fine in the database – my error was, I think, in the sanitizing part of the class.swpm-form.php.

Thanks for your follow-up!

Thanks mbr – I asked Stackoverflow yesterday.

Hi mbrsolution,

Thanks – but in fact that guy had a problem with not putting quotes (“) around his PHP echo statement, which was trying to pre-fill the field with a session variable.

In my case, I am not pre-filling the field with any value. The problem is when the user physically edits a member in the WP_SWPM backend list, by typing 82.50 into my custom field. After hitting Update, the field shows 99.99.

Very weird!

Okay – just to let you know: I diffed my Attitude theme files against the Attitude Child theme I use. (I did this when I found that Attitude allowed media uploads and inserts, but my child theme didn’t …)

My suspicion was that the offending code would be in the functions.php or in the header-extensions.php, where I had a secondary menu that I concocted. It was in fact the header-extensions.php.

The simple process of adding back Child theme code chunk by chunk, checking that Insert Media was still functioning, until the site looked and behaved normally, was all it took. So I am not entirely sure what was in the old header-extensions.php that made media insert crash … but it doesn’t any more.

I also noticed that Attitude doesn’t use certain template files any more, whereas I had them in my Child theme directory, so I moved those to an “unused” folder for good measure, always checking that my site was still working.

Hope all this helps someone!

I think there may be an issue with the fact that for the time being it is on a dev/test site that is a subdomain of another domain. In August I have to take it live … hopefully that will make the issue go away. (Media insert works on my other WP sites, which are all in their own main domain.)

Thanks for the suggestions.

Ok – I deactivated every single plugin, and still got the hanging, so no chance of uploading to a page.

I put back Simple Membership as it’s the key plugin, and then decided to try uploading via URL. Have never done that before because never needed to. This works, however!

Is there any way to reinstall the media library part of WP? I get a related issue when I go directly into the Media library and choose Add New. The dialog says “Cruching…” for ever and ever until I get bored and quit the library, at which point I find the image has uploaded to the library after all.

And that reminds me, although this may be unrelated, since approx WP 4.0 whenever I update to new versions of any plugin, it hangs while updating, and similarly, when I finally get bored and decide it’s not working, and quit the plugins page, I find that the plugin has updated successfully.

Does this ring any bells?

Okay – I still don’t know what happened, but since then I reset all the usernames to email addresses, AND the encrypted passwords, still using

$encrypted_pass = SwpmUtils::encrypt_password($plain_password);

as instructed, and this time it worked fine. Maybe the script crashed halfway through and I didn’t notice it …

Okay, I figure this out.

Attitude does indeed make this menu item available for mobile devices. The error was in my CSS, which contained this formatting:

#after-header-sidebar
{
    float: left;
    width: 100%;
    background-color: 05a9c5;
    position: relative;
}

#after-header-sidebar  ul
{

}

#after-header-sidebar li
{
    display: inline;
    list-style-type: none;
}

#after-header-sidebar a
{
    font-size: 16px;
    padding: 1.0em;
}

(I copied this CSS from someone else and made a few modifications to it.)

Solution: Comment out these blocks
#after-header-sidebar ul
#after-header-sidebar li.

That’s all!

Thank you amjanina! This worked perfectly!

Brilliant – very pleased after all my struggles.
SP

okay, i think i found the file of interest:

class-phpass.php inside wp-includes

for now i will try to use this!

Aha – got it.

Having created mem levels of 1 – Admins and 2 – Members, I needed to add the “2” again in the Level ID box.

So is there an answer to this question somewhere? I have enabled “Anyone can register” in WP settings, plus “Free membership” in Simple Membership, but still get the message:

Free membership is disabled on this site

okay – i think i’ve found it: my lousy ISP relies on Swisscom services and they have blocked 25. not only did i know that already, but it was my ISP who said change to 587 – which i confused with 567, which is gmail, which i didn’t want.

now i have put my SMTP port as 587 in the WordPress Mail settings, with SMTP authentication, and have been able to send one message via SP!

sorry to bother you – but maybe someone else from Switzerland will suddenly have this problem too.

doug, you second suggestion – re: the article at https://sendpress.com/support/knowledgebase/troubleshooting-sending-email/,

i had already read that before writing to this forum. there are 3 suggestions:

the first is try using Send Test Email, which i had already done immediately on discovering my sending problem, and got exactly the same dialog (Debug Info) saying the 3 ports were blocked and the mail could not be instantiated.

the second suggestion starts off “If all the appropriate ports are open …” so does not fit my case. the third is about spam folders – and i’m not that much of a novice! also, in my case, the mail does not leave the send queue at all.

p.s. the only reason i tried port 2525 was after trawling around on forums for several days, and finding a blocked port 25 problem dating back a few years, where it was suggested to use 2525 because some ISPs block 25. obviously it’s pointless for me to try 465 and 567 as they are blocked too.