charliejustus

Ok kewl I’m guessing it’s because the website’s in our cookies and browser history so the plugin allows us through? Is there a way to get around that?

Still good to be able to see that it’s working. Thanks man.

Interestingly, it only seems to happen if you port a staging site across and then remove the staging site code in wp-config. I just re-enabled it and it’s working fine now.

Found out what was going on. Wp-Disable is another plugin that doesn’t work well with Jetpack

Hi James, I’ve already done that several times, checked the database after and there are still remains of Jetpack flotsam and jetsam in there. Do you know this code I speak of? Was I smoking a particularly strong jazz cigarette that day? Help please.

• This reply was modified 4 years, 2 months ago by charliejustus.

Additionally, I tried the Jetpack Debug and it said the the required token was missing and to check XML-RPC. XML-RPC is totally fine. I just want to wipe the database and start again.

Actually, realised that I had put some CSS and not attached a screen declaration. Nothing to see here!

Have you tried using the display:none code attached to the particular class that governs the header image section? Something like:

.page-inner-title {display:none;}

The only other way would be to create your own page template in your child theme and delete the section of coding that creates that header. The above is a fairly rudimentary way of doing it as it still allows the header section to be created and then taken out by the CSS code.

• This reply was modified 4 years, 11 months ago by charliejustus. Reason: Additional information

PS it’s a DIVI thing again! Woo. Love those guys.

What does that have to do with donations? When someone makes a donation, the moment they make any mention of that here in support then they move into customer territory and cannot be supported by the person they donated to here. The plugin or theme author isn’t permitted to support any customers here and that does include people who donated to them looking for support.

How does this have anything to do with my proposal? Also, do you really believe that people who donate to a plugin don’t ask for support here? How do you know if someone has donated? Are they tracked?

And on tracking, do you really think that we’re not tracked by using WordPress or more specificallly Jetpack? That it isn’t feeding back what we do, how we do it and what we want to do with it? The whole thing will be being monitored otherwise how can anyone know how to improve things that they provide? We have to click buttons that allow the plugin makers to gather information about how we interact with their plugin. Google Analytics will be being pored over to see where they can make improvements, so to say that tracking should never be a part of this community can’t be right, can it?

You mean like the way it is now in the plugin page’s sidebar at the bottom under the word “Donate”?

Yes that’s what I wanted to change. It’s at the bottom, out of the way and not very obvious.

Like I said, I like the fact that this is free and open source and wonderful, but the more fiendish and complicated a plugin is, the more resources it will consume to keep it going. The idea that someone shouldn’t be recompensed for that is a bit unrealistic isn’t it? How else will plugins and plugin producers survive? How many plugins fall by the wayside because the people who created them just don’t have the time to dedicate to something they get no return on? The number of times I’ve had to change plugins because the one I was using hasn’t been updated in a year or more is crazy and to my mind shows that there is a natural cycle where a plugin becomes too unwiedly to carry on with.

I would think that a donation wouldn’t breed any form of entitlement and if it did, then it should be spelt out that this donation doesn’t give the donater any form of extra right to demand additional items. I’m fairly certain plugin developers would get just as many demands for improvements post donation as pre donation and they’ll be just as snarky as they were when the person hadn’t donated.

Trying to reward users who actually donate would just lead to more gamification and too much of that happens already

The tracking wasn’t as a form of reward for donation per se, just a way of allowing people who have donated to remove the endless nags about donating that now seem to litter the plugins we use.

Developers are constantly on at us to donate to allow them to carry on updating the plugin through nags that they put in their plugins. I think this shows that there is a need to support them financially and since GNU is a core concept here I feel the museum model is a good one to follow. Keeps things free for general use with people contributing semi voluntarily.

*Wanders off to get coffee*

Also, if you had read the code description I wrote, you would know the name of the plugin I am trying to modify.

I did ask them, they said it would cost serious money to make the changes I’m trying to implement. Hence the reason why I’m doing this myself.

I’m not asking about how the plugins interact, I’m just wondering if there is a standard plugin procedure that I’m not following, that would allow the scripts to be called. Why are they being commented out automatically in the head? Does WordPress need certain things to be in place for it to work?

If I can get some help getting this code to work, then I can carry on with creating the plugin myself.

Has there been any movement on this? I’ve noticed the same thing on one of my websites. I’m hoping it’s a theme thing and it needs to be addressed there, but wondered if you’d managed to figure out if there was any one culprit @miketurnermk ?

Ok cool, I found this wordpress plugin, which you could use as inspiration to make it possible in a future update.

https://github.com/lumpysimon/wp-force-password-change

I’m going to have a play with it and see if it plays nicely with bulk uploads.

Figured out how to draft a form, it doesn’t make a lot of sense not to have that funcitonality within the form 2 post section itself. Could you add it to the metabox in a future revision?