ride2719

Oops this editor did the same thing, i.e. it replaced the ampersand-lt; and ampersand-gt; with the two characters. The sentence with <‘s and >’s doesn’t make sense for this reason. Obviously my attempt to use html character encoding is not helpful.

I am having the same problem with exactly the same error report when trying to add code to the footer. I tried replacing < with < and > with > and the plugin editor seemed to like it, however when I clicked the save button it replaced the ampersand codes with the original characters. However it did save the code, but when you look at the page the php snippet did not do anything. I was trying to produce a copyright notice using PHP to insert the current year. It looks like this: “<p>&copy 2014 – <?php echo date(‘Y’); ?> mysite.org</p>” — trying to produce “copyright 2014 – 2022”. Needless to say, it is important to be able to insert PHP scripts.

I’ll be working on your suggestions today — Thanks very much. I’ll report on my success (or not) with specifics.

The comment about frontend uploaders has a typo. I was trying to say that I am not committed to FU, but am open to using any frontend uploader that is easy for non-technical users to use and that makes linking to MLA as straightforward as possible. My choice of FU is based on a more general assessment that it seems to be a plugin that has been well-implemented and that has a lot of flexibility, AND I like the UI.

I actually pre-date C. My career was built on FORTRAN and assembler, with a little bit of COBOL and Visual BASIC along the way. Getting into web design has been both fun and challenging for me. (It’s hard but not impossible to teach an old dog new tricks.)

Thanks again for your very kind attention to my question.

OK I figured it out. I had set up an external cron job to trigger Postie. The request was being hijacked by some home-grown code that was looking for access from users that are not logged in (i.e. you must be logged in to use the site), and it was routing the request to a log-in page before wp-cron was invoked. I wrote the check because I could not find a plugin to do this as comprehensively as I wanted it.

The think that confuses me is that it WAS invoking a page, i.e. the log-in page. All the documentation I’ve seen to this point says that if ANY page is accessed that cron will be invoked — I have not disabled the normal cron logic.

To be a little more precise:
The external cron job invokes:
https://<domain-name>/wp/<sub-site-name>/wp-cron.php
The internal log-in check reroutes the request to:
https://<domain-name>/wp/<sub-site-name>/log-in
I checked and the cron job is in fact receiving the log-in web page as output from the server (which of course was not seen by a person). When I excluded the cron request from the log-in check Postie started working.

Can anyone tell me why the invocation of the log-in page did not trigger Postie?

Thanks.

OK, sorry to whine but I am seriously stuck on this. I have:
— reinstalled the plugin
— disabled all other plugins except akismet
— set up an external cron that seems to be working
— tried manual posting which works
— checked settings multiple times
— I have read and implemented stuff according to the “Postie Not Checking Email” article on the postie site.

Can someone please help??? TIA

OK, I got it to work with sendgrid, but I’m not sure what fixed the problem… I changed a number of things trying to get it to work.

Sorry, here are some additional information:

WP 4.4
multisite

Also, I tried the sendgrid plugin. It picks up and sends notifications from other plugins, but it does not send mail from Post Notification by Email, i.e. it sends NO email at all.

When I de-activate the sendgrid plugin, Post Notification by Email DOES send out the post email to the subscribed list.

Here are a couple more bits of information that might be relevant:

–This is a multi-site
–I had to change the cron job url from the one that
MP gives in the “geek” section, due to the fact that
it is a multi-site. If the 32-byte hash has any
dependence on the url, this would be a problem.

Cron job given by MP:
https://letipmail.letipwestshore.com/wp/members/wp-cron.php?1eafd1b8dc6a4abac892a899919ff7f7&action=wysija_cron&process=all

Modified for multi (i.e. there is only one wp-cron at the
root of the wordpress installation:
https://letipmail.letipwestshore.com/wp/wp-cron.php?1eafd1b8dc6a4abac892a899919ff7f7&action=wysija_cron&process=all

–As you can see, WordPress is installed in a subdomain
(can’t imagine that that this would have anything to do
with it).

Yes, that was it thanks.

It might be obvious, but I just didn’t see this important detail.

Thanks again, Rick.

OK — I found it. SORRY again. It was under the MS tab.

SORRY — the last paragraph should read:
This is a serious problem, because the “info” address is showing up in the emails and it does not exist, and CANNOT be be created. Is there a way to fix this?

Thanks for your response jazzigor. I really appreciate you remaining engaged, particularly when discussing a hack. Until there is a better way, this approach creates a form that looks consistent, and that preserves place marker insertions, which is what I needed. It could also be a template for creating other special fields. I’m looking forward to the evolution of this plugin.

I’m thinking this has gone as far as it needs to go (further, I’m sure, in the opinions of some). I’ll mark it resolved.

OK, I decided to go ahead and create a demo page showing the use of the JSColor color picker. It seems to me to be generic enough that it might be helpful for anyone trying to implement a special field type in Jazzy Forms. Here is the link:

https://stuff2help.net/demo-color-picker/

Thanks for your response. What you describe is what I thought I was doing.

I put the (visible) color picker into a free Jazzy HTML element, and styled it to look like a Jazzy Form element, for example, with the use of the label tag and the jzzf_element_label class.

The form also has a hidden Jazzy Form element (with ID csscolor). For this to work, you have to figure out the internal ID of the element (in this case, jzzy_1_csscolor). I use Chrome for this. The onchange event trigger takes the color code from the picker field and puts it into the hidden Jazzy Form field. It is the Jazzy field that I use later on with a {{csscolor}} place holder.

The form looks good and works well with the use of a Jazzy update button. I half expected the onchange event to trigger the “instant” update, since it is changing the value of the Jazzy field, but it doesn’t. I fooled around with code of the form document.getElementById('UpdateButtonID').click to trigger the Jazzy update button, but it is very context specific and I haven’t gotten it to work yet. (I am not an experienced javascript programmer.)

Supporting the instant update feature is not critical to my project: it would just be nice to do. Jazzy Forms made it possible to do what I need with almost no code. I really like the plugin.

I’m not ready to show the actual page where I implemented the color picker. I’ll try to put together a demo page and post a link to it, but that may not happen for a while.

Thanks for the great foundation you have provided with version 0.11. If I am able to generate any income from this project, I’ll certainly donate to your effort.
Rick.

That’s really interesting… I tried grofscala’s suggestion and it fixed most of the problem.

Radio buttons are being rendered with the bullet symbols (from the list formatting).

I have an iframe (discussed in an earlier post) that is in an html element that is being rendered too narrow. The CSS I used to fix that problem works in other browsers but does not work in FF.

But, it’s MUCH better — the elements are together in rows the way they were configured.
Rick.