athenaofdelphi

This issue has been sorted. There is brief explanation of the issue and the solution here in case anyone else is having a similar issue.

Hi mschefers,

I got an email from my blog about your comments last night and have sent you an email describing what I believe may work. Please can you let me know how you get on with what I proposed.

Regards

Athena

Hi justplaindoug,

Location add on? Can you elaborate on what that is. Are you absolutely sure it’s ACFW and not the Advanced Custom Field plug-in which provides a bunch of advanced custom field functionality?

Regards

Athena

Hi Deyneko,

I’m running WP 3.8.1 on my own site which has more than a few instances of the widget and it seems to be working properly. As yet I’ve received no complaints about it not working with 3.8.1 from anyone.

Am I still looking after the plug-in? The answer to that is yes, but my job pays the bills so unfortunately the plug-in does take a back seat. Rest assured that if it gets to the point where a new WordPress release doesn’t work with it, I will get it sorted. There are quite a lot of people using it and I wouldn’t want to leave people in a mess.

Regards

Athena

Hi netsolution,

I was hoping to have a quick fix for you, but unfortunately this is down to how the Advanced Custom Field plugin stores the text from a WYSIWYG field.

I’ve just added ACF back to my development blog, and it appears it doesn’t store the HTML as you might imagine. I’ve just taken a peek at the postmeta table and the data being stored is filtered. It’s doing some sort of conversion on it that is resulting in the paragraph tags being removed. Even with the content filtering disabled.

My widget shouldn’t filter HTML as I use it to display HTML myself.

Sorry I can’t be more assistance.

Regards

Athena

Following an email conversation, this issue has been resolved and Kenneth is happy with the solution.

Hi Kenneth,

I’d like to send you a version of the widget that may fix this… can you drop me an email to “a t h e n a at o u t e r hyphen r e a c h e s dot c o m“. I’ll send you a version of the widget that should fix this… if not, I’ll set up a test on my development blog and look at sorting it out for you. More details in the email when I reply back directly to you.

Regards

Athena

Hi Kenneth,

Sorry for the delay, I don’t get notifications from here when someone posts, this is why I ask users to post on my blog.

Anyhow, can your provide a bit more detail… which random quote plugin for example so I can look at setting up a test on my development blog.

Whether this is the proper tool, based on what you said, I believe you should be able to achieve what you would like, but I do need more information about the plugin you’re using for the quotes.

Regards

AthenaOfDelphi

Hi bigiaim,

I actually sent you a mail about this issue, please can you let me know whether you’ve received it or not.

Thanks

AthenaOfDelphi

Hi rolfo,

The widget shouldn’t display anything at all if it’s configured correctly and there is no data in the field. Please can you grab some screenshots of the configuration for the widget and email them to me (athena at outer hyphen reaches dot com)?

I’d like to see if I can fix the problem for you.

Regards

Athena

No further comments/actions on this request in about 9 months, so I’m going to mark this thread as resolved.

Firstly, I’m sorry you’ve been unable to get ACFW working for you. It’s not suited to everyone’s need and yes, the interface could be improved which is why I’m taking my time with a new version that has a completely redesigned interface.

My plugin is not affiliated with Advanced Custom Fields, I didn’t even know about that plugin when I named this. It is so called because it is an advanced extension of the custom field widget originally written by someone else.

But, with all that said, I’m disappointed and saddened that you’ve made the statements above without so much a single email or comment to me (at least that I’ve been able to find). I take great pride in trying to help everyone who has a problem with my widgets and it clearly states at the bottom of the widget control panel that if you get problems, to drop a comment on my blog. As a result of such comments I’ve spent a great deal of time helping potential users and in some cases writing new plugins to solve their particular problems.

Instead you’ve elected to simply make derogatory remarks which actually cast a shadow over what I’ve tried to do since releasing this widget, and that is to help everyone who wants to use it but who has problems, so thanks for that. As a side note, the user documentation has actually been reviewed by a number of users who have successfully deployed the widget without any assistance from me (they only got in touch with feature requests and helpful suggestions on how to improve things).

If you’d still like to use the widget, then drop me a mail or a comment with your specific questions.

Regards

AthenaOfDelphi

Hi polins,

The problem is the ” characters that can be embedded in the content.

Depending on how you use the widget, you may be able to fix it by changing this line:-

eval( '$cvalue="\n<div class=\"advcustomvalue\">\n' . $cvalue . '\n</div>\n";' );

To:-

$cvalue="\n<div class=\"advcustomvalue\">\n".$cvalue."\n</div>\n";

However, you should be aware that this can prevent the replacement of strings like ‘$acfw_content’ in the content generator.

I can’t offer an updated version of the widget at this time because of the potential for it to break other peoples sites. I have a possible solution, but I just want to be sure it’s going to work.

Hope this helps until I can provide a more permanent solution.

Regards

Athena

Hi polins,

Apologies for the delay in responding… I don’t very often check the forums here.

I’ve just checked the codebase and it should definitely pass the content through the short code processor. Can you provide more detail, like details of the plugin that provides the shortcode, the shortcode itself etc. so I can look at setting up a test on my development blog.

If I can reproduce the problem, I should be able to fix it.

Regards

Athena

Hi bluebird2,

Scratch my question… my plugin won’t work with ACF because the data is not stored in the standard location for custom fields. ACF has it’s own storage mechanism. To use the data it holds, you must use it’s built in template functions as described in the user documentation for this plugin.

This use of a custom storage mechanism is why the custom field display widgets don’t work with it… I suspect they’ll all use the standard custom field storage mechanisms.

Regards

AthenaOfDelphi