Dave Liske

Tobias, Thank you for the reply!!

I do have an inkling of how to go about doing this as a plugin via your plethora of hooks, so I’ll go ahead and begin working on that with your current Github version. Once you release 3.0, I’ll ensure the Category plugin is compatible, and email you the Zip.

Thanks again!
Dave

Wow, I could not have gotten that more wrong. We’re back to the drawing boards. Good thing I didn’t actually release that … I’m crawling back into my cave for bit …

IvanRF, we have Defaults working for the next version, please see the working examples at:

https://micuisine.com/content-block-plugins/2015/11/08/using-variables-within-content-blocks/

This issue seems to come and go, regardless of the number of suggestions there are for fixes. This will be the third batch of fixes since I took the plugin over. I’ll ask the hard question: What is the consensus for removing TinyMCE and simply using a textarea instead? That would certainly resolve this.

I like it, I’ll get to work on it. Thanks.

Ah, gotcha, let me think on that a bit. At the moment it displays “My name is %%name%%” if it’ empty. Your code might be able to test for this somehow, not sure how you’ve written it. If that doesn’t work I’d need to set some sort of flag.

Hi Rob … I have no plans on doing so, since talking to one other plugin means talking to many others. I’d rather keep it simple, and not have to deal with that kind of complexity.

Hi IvanRF, just replied to your empty variable question. No, I’m not using GitHub, at least not yet. I’m thinking a complete rework is in order, so I’d rather the project have a better stsus before then.

Hi IvanRF … In thinking this through it almost intantly becomes unwieldly. Where does the default value get declared at? The Settings page makes the most sense. But then the other possibilities present themselves, such as %%address%%, %%city%%, %%email%%, %%standardprice%%, %%exesphonenumber%%, %%requiredmilkfat%%, %%milestonextpineapple%%, and anything else that might be needed. Do we then allow an (almost) unlimited array of defaults, the same as the blocks themselves? Do they also need an import/export? Or did you have something else in mind for the mechanics of it? I’m definitely open to suggestions, this one might be headache-worthy though … ??

Hi brighttribeblog … Are you using the current version? TinyMCE is likely what’s causing this. I’ve modified its settings quite a bit, but honestly may end up replacing it with a text area instead.

I’m currently testing version 2.1.6, which bases the pages on admin.php instead of the current options-general.php. I’ll be doing a release by … January 19th. I’m hoping this is the solution.

IvanRF thanks for this, finally doing some testing on version 2.1.6 which includes these suggestions.

Hi romanalbertini … There’s really no way to do this. I’m planning a method for creating multiple content blocks for version 3.0.0 but it won’t be what I think you’re asking. It’s also at least a month away.

If you need to have a live chat window open I’d look into something like LogMeIn that has its own floating window. Doing something inside WordPress really isn’t practical.

Hi lancem631 … Because of security and other issues in doing so, that’s not something I would support.