Editing Post – text and media not visible

FYI: Install is using all the default settings. None changed.
Using only text to display a message under title in Posts
Pages etc not used.

I apologize for the issues you’re having with this plugin. However, I am not able to replicate any of them.

I do believe I know where your problem was occurring with the 1.3.02 update. This was my fault — I actually changed where the data is stored in the database to better accommodate the plugin name. When I made that change, all old data was lost. I realize now that it was an unnecessary change, and I’m sure it caused problems for more than just yourself.

Going forward, you should not experience that problem again.

I urge you to give this plugin another shot, as it has been working on one of my multisites for a number of months now (I finally turned it into an actual plugin). Once content is added to the page/post editor, it replaces the default setting you set… so updating the plugin settings will not effect your added content.

Thanks for the report,
Dave

Thanks for the reply, have updated to 1.033 on localhost
No change to missing content in new / old posts.
same issue with various themes eg Twentyfouteen / Thwentyfifteen.
same issue with WP4.01 (fully hosted site and localhost)
deactivated all other plugins on localhost Wp4.01 and WP4.1 RC1
Same issue with both Wp versions
all using php version 5.4.34 fast-cgi

await fix before reactivating (happy to beta test for you)
(workaround = added a metabox message in child theme functions.php )
but prefer this plugin, as other (none tech) admins can alter these messages. good luck.

Hmmm, I’m still not able to replicate. I’ll keep working at it.

I’m glad you found a band-aid fix for your site, while I work out these issues.

I am working to give this plugin some conditional logic that may alleviate this issue for you and others. So, on the settings page, you would need to check a box to enable a certain feature. If the box is unchecked, that feature will be disabled (even if there is text added to the option). In this case, disabling the WYSIWYG feature would solve your problem.

Let me ask you – are you using the WYSIWYG feature (or are you trying to use it)? I’m thinking about removing this option and keeping the plugin strictly for adding instructions. I would, of course, create a second plugin that deals only with the WYSIWYG feature.

I’ll be sure to add you to a beta test list, once I get some new code in this plugin. For now, you can always follow development at the plugin’s github page – https://github.com/dauidus/add-post-type-instructions.

Oh, and I believe I’ve finally replicated your issue! It seems to happen after deactivating the plugin and then reactivating it again. So, I have a place to start.

isn’t debugging fun, NOT ??
Basically I would use your plugin is to offer basic howto’s /info.
For example with our the Magazine style front page the “feature image” is important, all of our authors seem to miss out this step, resulting in their front page article/post lacking that “visual read me pull”. The blog admins re-edit and add one for them (time and effort) So you can guess what my custom message contains.
———-
Do i want default text inside the metabox? Maybe, the benefit is that it saves screen space over the static message. + I’d use html to add a basic image and some info text, (which i hope they would replace… !!)
—-
Would an extra metabox be better than a static message of standard text? (not sure to be honest, probably not) the one benefit is it would be visble to new users who need the instructions and older users could hide the metabox. So along with this idea, would it be possible to collapse the message to free up the writing space (think smartphone users) ?
–
A thought has just popped into my head – have you tested your plugin with WP4.1 (with the focus plugin = distraction free writing ) not sure if this will change how your plugin functions.

pix365,

I’ve done some pretty extensive testing on this and have narrowed it down to what I’m calling a ‘bug’ in WordPress. In all my tests, on multiple past and future versions of WP, the content both saves and replaces empty content values perfectly, as long as a title is set on that page/post.

If no title is set, WordPress seems to have trouble associating empty content with that page/post. This makes sense, as long as no other options or settings were modified on that page/post. But, that’s where the bug comes into play – WP doesn’t respect that other data and assumes there should be content. Add a title to that page, and you should be good to go.

Is this consistent with your experiences with my plugin?

I am working on a work-around for this issue that uses AJAX. But, it won’t be out for a week or so.

I have, however, added options to each setting field that allows you to disable each feature individually, but allows you to save text in each field. It can be found on the Github repo.

Thanks again for your patience and bug reports. ??

Dave

pix365,

I have fixed this bug and added some new features to version 2.0 that I’m sure you’ll appreciate. Thanks again for your help in determining the issue at hand!

With all the holiday rush, I have decided to delay a 2.0 update until next weekend, at best. Until then, you mentioned you’d like to beta-test this plugin. Please find the Github repo in a previous post. You may download the plugin zip on the right and install it like any other plugin. It should be fully-functioning (though, with the update you’ll need to revisit the settings pages and check each field to enable them.

Cheers!

I was thinking my localhost setup is part of the issue.
new WP test site setup, waiting for DNS to propagate subdomain.
I will test on WP4.1, + I have to do this anyway to make sure 4.1 does not screw up anu of the live sites.
All live sites are WP standalone not WP network
I will use native english WP, test and migrate over to french and test.
I will then create the fr_FR.po / mo files.

Enjoy the break.

Git Zip uploaded to dev site 20 dec 14
No issues with published articles (on both WP4.01 or WP 4.1)
all plugins then activated. (fully replicated the live site) No issues.
—
Used html and plain text): Messages all appeared as per html code.
— FYI.—
Message under the title.
Asthetic issue 1
I would prefer to have less padding at the top margin
it looks as if i had added in an extra <p></p> before my message text.
—
Asthetic issue 2,
IMHO, plain text size is little large without using html.

—
great job,, Thanks for your efforts.
Rgds Terry

Terry,

Thank you for the feedback. I’m getting very close to a public release of version 2.0 and can’t thank you enough for your comments and testing.

I also feel that Aesthetic Issue 1 gives a bit too much padding at the top margin. But, this is strictly due to the way WordPress handles an empty title field on newly created content. Add a title and save the draft, so that the slug field appears below the title to see what I mean. WordPress reserves that space for the slug, even if the slug doesn’t display yet. Kind of annoying, I agree. I’ll look into ways that I can make this empty space seem smaller.

As for Aesthetic Issue 2, are you referring to just the text below the title, or throughout the whole plugin? I have toyed with using smaller text below the title, but I feel its easy to miss noticing it. Perhaps my next major release will alleviate the problem – I’m looking to provide a way for users to hide/unhide each instruction.

This plugin will remain under active development, and I will continue to look at these issues as development progresses.

Thanks again!
Dave

Re Issue 1, “Add a title and save the draft, so that the slug…”
Think about the workflow of new-post. you don’t have slug at that point, so I think another default method is going to be required if you wish to reduce or remove the padding.
— I took a quick look at my workaround code,
— It has the same padding issue (I never noticed before..humm )

Issue, 2 It’s a generic thing,
I agree on small fonts can be missed that’s why I used Color and <srong> as the visual pull.
I ended up using h5 in the html for an attactive size.
editor-style.css in my theme uses this
h5 {
font-size: 13px;
font-size: 0.928571429rem;
Hope this helps..
—-
Hiding stuff?
If it worked in similar method to metaboxes, (where a users preferences are remembered by WP).
For frequent posters – thats fine but for casual posters, i.e those who post say every 3-4 months – they will forget they hid the message(‘s) and it’s normal. These users kinda defeat the reason for the plugin, which is offers some quick tips’s (well in my case that it is).
Have a think about your audience. Regular frequent bloggers versus casual posters.. maybe admins activate the ability to allow users to hide measages or they are forced visble to everyone. (or to various roles)
———————–
I have the GIT plugin on a live site deactivated, still using my workaround, 2 reasons why
1st I would prefer a full production plugin, (but the dev version is ok) & 2nd I need to talk and educate the blog owner about the plugin before she uses it. (she has some very strange rules about tips and messages = my problem.)
Rdgs Terry.

fyi: Inspected element. When using plain text.
——-
#poststuff h3 (wp-admin/edit.css line 605)
added override to apti-css
Line 1 = #poststuff h3 {
font-size: 85%; (orig is 14px)
padding: 8px 12px;
margin: 0;
line-height: 1.2; (orig line is 1.4)
}

this worked for me, & probably backward and forward compatable.
Ok I know it’s not elegant. but not found any issues creating new posts/pages/comments/bbpress topics.

Terry,

Wow… you’ve really been looking into this! I’m glad you’ve found this plugin useful enough to extend/modify it on your own!

But, as the original support topic has been resolved, this is not the appropriate place for suggestions/code additions. I am very much interested in learning how I might make this plugin better. But it could get pretty confusing to add all that info in the plugin’s WordPress support forum.

Instead, I suggest opening an issue on the plugin’s Github page https://github.com/dauidus/add-post-type-instructions/issues. I have created the first issue, where more information can be posted.

I have also created a Github Wiki for this plugin https://github.com/dauidus/add-post-type-instructions/wiki. I’ll do my best to keep it updated with planned features and changes.

Better yet, you could fork this plugin and commit your own changes there. I find it helps to create far better collaboration and makes it easier to see what changes have been added.

Thanks again for your efforts and I look forward to seeing you on Github soon!

Dave