471 comments found.
Hi, do you have to an estimate for a fix for
https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/wp-user-extra-fields/user-extra-fields-170-unauthenticated-arbitrary-file-deletion?
Best regards, Michael
Hi,
It was affecting the 16.8 and was already fixed in 17.0, but Wordfence and their update communication system with authors is awful. Please update to 17.1
Thank you for the update—Michael
i add an html field, how to hide the place holder text
For that you need to edit the templates you find in the templates folder inside the plugin.
For example, if you are displaying the field in the woocommerce checkout page, you need to edit the woocommerce_checkout_form.php. Find all the occurrences of the “placeholder” attributes and remove fthem rom the template.
Hello,
1) it is possible to allow the user to edit fields only on the checkout page but on the profile page only the admin can edit it? 2) the field file on mobile can allow the user to take picture of file with camera and upload it? 3) can we block checkout with fields. Eg: i want to block checkout order until some fields or files is approved by admin.
- You can enable the option to display the fields only in the checkout form: https://ibb.co/Dggc6k10 . The admin can edit the fields via the WordPress admin area, Users -> User profile page. Before any purchase, use the demo site to see if the plugin actually works as you expect
- I’m sorry, the plugin doesn’thave have such a feature
- I’m sorry, the plugin doesn’thave have such a feature
The fields of the plugin don’t show on woocommerce Blocks Checkout. Thanks to support if possible
Yes, because WooCommerce blocks doesn’t offer any PHP action or filter that allows third party plugin to render they’re data. You need to switch to the default WooCommerce checkout template.
Hi there, I updated php and wordpress and this messages appeared:
Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /www/hlifeshop_430/public/wp-includes/functions.php on line 7329
Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /www/hlifeshop_430/public/wp-includes/functions.php on line 2189
I found that are generated by interaction with WPUEF plugin (it is updated to last version). Do you have a patch?
thanks
Gianluca
Hi Gianluca, In the errors you reported, I do not see any reference to the User Extra Fields scripts. If you report which script and line is actually generating any issue, I’ll be glad to fix it.
Hi, is this plugin still working with latest wp version ?
As installing it doesn’t allow to find the plugin into the menu. The only thing that appears is into the settings, user extra fields.
But doesn’t allow to create anything, as the screenshot show the red buttons.
Thanks
Hi,
yes it works. For any support, however, you need to have a valid purchase and support licenses associated with your account.
Hello,
We have WPUEF running for some years now. Today I bought a new license v16.7 and installed it by overwriting the existing plugin. Now I cannot edit our existing extra fields any more, what I get is an empty screen on the Extra fields configuration page.
On the frontend everything still looks fine though.
How to get access again to the extra fields configuration?
Thanks, Rainer
Hi Rainer,
It sounds very strange. Furthermore, the screen you shared has a broken link.
define( 'WP_DEBUG', true ); define( 'WP_DEBUG_LOG', true );reperform the test and see if more clues are reported in the debug.log located in the wp-content folder.
Thank you
Thank you. Here again the screenshot:
I cannot find anything connected to wpuef in the debug.log file. Here is what I get:
[13-Dec-2024 09:45:15 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the product-open-pricing-for-woocommerce domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /www/htdocs/w00972c9/registration.thomashuebl.com/wp-includes/functions.php on line 6114
[13-Dec-2024 09:45:15 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-mail-logging domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /www/htdocs/w00972c9/registration.thomashuebl.com/wp-includes/functions.php on line 6114
[13-Dec-2024 09:45:15 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the complianz-gdpr domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /www/htdocs/w00972c9/registration.thomashuebl.com/wp-includes/functions.php on line 6114
[13-Dec-2024 09:45:15 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ninja-forms-user-management domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /www/htdocs/w00972c9/registration.thomashuebl.com/wp-includes/functions.php on line 6114
[13-Dec-2024 09:45:15 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-gateway-stripe domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /www/htdocs/w00972c9/registration.thomashuebl.com/wp-includes/functions.php on line 6114
[13-Dec-2024 09:45:16 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-mail-logging domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /www/htdocs/w00972c9/registration.thomashuebl.com/wp-includes/functions.php on line 6114
[13-Dec-2024 09:45:16 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the complianz-gdpr domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /www/htdocs/w00972c9/registration.thomashuebl.com/wp-includes/functions.php on line 6114
[13-Dec-2024 09:45:16 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ninja-forms domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /www/htdocs/w00972c9/registration.thomashuebl.com/wp-includes/functions.php on line 6114
[13-Dec-2024 09:45:16 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ninja-forms-user-management domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /www/htdocs/w00972c9/registration.thomashuebl.com/wp-includes/functions.php on line 6114
Unfortunately, that’s only a notice not even related to the plugin.
Could you check the browser error console and see if any further clues have been reported? Could you also try disabling the other plugin and see if you still experience the issue?
What I found out in the meantime: when I open the WPUEF configuration editor with Chrome, it seems to work. The problem only occurs with Safari. The Safari console messages:
I’m sorry, but as you can see from the plugin page, the plugin officially doesn’t support Safari due to its unreliability in managing HTML5 standards. The supported browsers are Chrome, Firefox and Edge: https://share.nmblc.cloud/3d5f2499
Pre-sale question: Can I add ‘conditional rules’ to field to hide/show in registration form. Ex: if ‘Field A – Checkbox’ is checked then the ‘Field B’ is ‘shown’ otherwise ‘Field B’ is hidden. Thanks.
I’m sorry, you cannot. The plugin doesn’t have such a feature.
I can eventually implement a customization for this. If you send a private message (click on my name then use the low-right box) reporting your email address and a detailed description of your scenario, I can evaluate its feasibility and give you a quotation.
hello,
How can we create a field that will accept an existing shortcode in it?
I am trying to provide a field to be used in buddypress that gives the user a shortcode instruction for them to place that shortcode into a user field and have that shortcode outputs correctly in the users profile.
unfortunately when I try and use a shortcode in any of the Extra fields from Text area, text field or html field when the user enters the shortcode and saves it the results on the edit page are the shortcodes raw output not the expected saving of just the shortcode given and that shortcode output is a full scrambled raw html code. then on the profile page in front end it shows the shortcode output however in a total mess which repeats endlessly down the page.
You mean a shortcode as user input? or in the description?
In the first case, you cannot. Shortcodes are not meant to be used in that way.
Hello Vanquish,
The demo: https://www.codecanyondemo.work/wpuef_wp/ doesn’t work with demo, demo.
Is it possible to add extra fields to WordPress backend user profile pages? If yes please send a screenshot.
Thank you, Andsmith
Hello,
sorry for the inconvenience. Please retry now.
- when saved, fields are prefixed with this unicode value. So each meta has a 3 char prefix. I think i could live with this after cleaning metadata field in db and with a wp filter to sanitize new fields before them to be save
- but i just saw that there is a side effect also on rendered forms, as the default value for fields is ‘value=”​”’. And so, the mandatory condition does not work any more as the field is already set
I think this preset should be removed from your code, and you should consider other ways to prevent autocomplete (such as autocomplete=”off”)
Consider also that metadata fields of your other customers could have been prefixed, and a cleanup could be necessary. I can share you me cleanup code if you need it
I’m sorry, but other methods are completely ignored (like for example the autocomplete=”off”). This is why this particular method was used.
If you share the cleanup code I can include in the next version.
But this does not fix pb of mandatory fields that are not managed. At this time, i cloned the template with the fix (but cloning is not a solution because i loose your next modifications) special_blank_character=”” Perhaps a js validation could restore the mandatory rule. Or make this special_blank_character optional (don’t know why this feature appear, but seems that drawback of the fix is greater than the original pb itself)
Thank you for sharing.
Hello,
On the plugin page, it states that there is a custom shortcode to be able to place these extra fields on any page. Where am I able to find that shortcode to place on any page? I can’t seem to find it.
Thank you, Bill
Edit: I found the shortcode, but the fields aren’t displaying properly. Some of my fields are set to half width and others are set to full width, but all the fields are displaying full width and not next to each other like they are in the account details page.
Please help
Hello,
in this case it could be that your theme is defining some CSS rules that are interfering with the ones use by the plugin.
For this, use the browser inspector tool, see which stiles is your theme associating to the fields and then modify the theme css (or override the CSS rules) according to your need.
Salve, ho acquistato il plugin ed inserito i vari extra nel mio sito. Nella pagina di registrazione, però, non le vedo comparire.
Da quel che ho capito dovrebbero comparire automaticamente. Posso chiedere una mano?
Grazie mille
Il sito in questione è b-cp.it/my-account
- nuovo campo: https://nimb.ws/Gz60C8
- pagina registrazione: https://nimb.ws/Gz60C8
Per capire se il malfunzionamento che stai verificando dipende da un bug del plugin o da una errata configurazione (piuttosto che da un interferenza da parte di altri plugin/tema), per favore, utilizza il seguente sito: https://codecanyondemo.work/wpuef/wp-admin (user: demo, pass: demo) e ricrea il tuo scenario. Fammi sapere se l’errore si verifica, cosi da condurre ulteriori test.
Ho provato a creare un nuovo field, ma giustamente non essendoci woocommerce la pagina “my-account” non è presente.
allego screen del mio sito:
- pagina wp-admin—> registrazione https://nimb.ws/wOPDKN
- pagina my-account—> https://nimb.ws/M5mHjO
Fino a qualche settimana fa funzionava correttamente, aggiornando i vari plugin del sito ora non vedo più i fields
Si, puoi accedere alla pagina registrIone/my account attraverso il link “login”
Ecco la pagina: https://codecanyondemo.work/wpuef/my-account/
Per favore effettua il test e fammi sapere.
Effettivamente nel tuo wordpress vedo le modifiche, cosa che invece nel mio non accade. Dovrebbero comparire in automatico in entrambe le pagine, corretto?
Si esatto. Se non accade è perchè o si è attivato un opzione che restringe la visibilità (come ad esempio visualizzare campi nella pagina checkout) o perchè qualcosa ne impedisce la renderizzazione (ad esempio nell pagina di registrazione non viene lanciato l’action “register_form”. Questo impedisce al plugin di sapere che il form è stato renderizzato e quindi inserire i propri campi).
La seconda causa di solito è dovuta a plugin terze parti o al tema.
Ciao Vanquish, ho trovato l’inghippo. A quanto pare non appena abilito Yoast SEO (basic o premium è indifferente) si presenta l’errore!
Grazie per aver condiviso il risultato della tua ricerca! Dovresti eventualmente riportare il problema allo sviluppatore.
Lo User Extra Field si aggancia all’action user_register. Quel plugin sembra interferire, ma non saprei in che modo. Prova a riportare il problema allo sviluppatore per vedere se loro hanno qualche idea in piu.
How can I download the previous versions?
You cannot, CodeCanyon doesn’t offer offer option.
the page “Extra fields configuration” show a blank page when I go to Wordpress Admin => Users => Extra Fields
Without any further clue, it is quite to say.
please enable the WordPress debug mode and debug log ( https://wp-staging.com/docs/enable-wordpress-debug-log-mode/ ). To do that insert the following lines in the wp-config.php you find on the root of your site:define( 'WP_DEBUG', true ); define( 'WP_DEBUG_LOG', true );reperform the test and see if more clues are reported in the debug.log located in the wp-content folder.
I don’t see issues in the log. This is the screenshot of the blank page: https://drive.google.com/file/d/1KLL_HUYup_qH0NJfHLnG1yp43TD4l5IL/view?usp=sharing
This unfortunately doesn’t add any clue. Try to disable the others plugins and see if any of them is interfering. Try switching theme as well.
Try also giving a look to the browser error console to see in any further info is reported.
I disabled all plugins and switched to standard WooCommece theme Storefront, but still get the blank page.
When inspecting the HTML file, your formbuilder contains nothing.I also tried to delete the plugin and re-install, but it does not affect. The blank page still appears, and the previous user extra fields were not deleted.
I guess something wrong in the user meta data.
Can you instruct me how to remove this plugin and all related data like database and meta data totally? I want to clean all user extra fields and re-install your plugin from the scratch.
Thank you.
The page you are trying to access (the user extra fields options page) hasn’t anything to do with the usermeta data. The options data is stored in the options table and is managed independently from the user data (stored in the user metadata table).
If you send me via private message (click on my name and then use the low-right box) the following data:- your email address
- full admin access to the wp-admin area
- FTP access
- A detailed step by step guide on how to experience the issue
I can perform some further tests to see if it is possible to determine the cause.
If you wish to delete all the data, just log into your database (with tools like PhpMy admin) and in the wp_options table, delete the following keys:- wpuef_options
- wpuef_general_options
Regarding the user meta, delete all the metakey you find in the usermeta table that has as a prefix the wpuef_cid_ string or just use the following option: https://nimb.ws/rA4OJu
After deleting all extra fields as your instruction (https://nimb.ws/U2Zx1d), the plugin returned to work as usual. It’s done. Thank you so much for your support!
Glad to hear that! 
last but not least, I would ask you to help me: If you enjoyed my efforts to assist you and/or my plugin please consider leaving the 5 stars…It would help me with sales, I would really appreciate it!
(to leave a rating: go to your profile page, click on “Downloads” and from there you can rate your purchases.
You can also leave the rating through the plugin description page: https://www.dropbox.com/s/v6zaoe0p6cs4x2o/rating.png?dl=0 )
Have a great day!
I found the solution
Glad to hear that
Hello,
I use: $result = wpuef_get_field(‘c13’, 16669); var_dump($result->value);
result is string(15) “0173-8058817”
how is the php code to get only: 0173-8058817
I can not use shortcodes because i use php
Purchase Code: 7ec3d81a-c5f3-4d27-9322-8f2b799ee563
Fields not updating (not keeping the data entered) upon save. Also with this plugin enabled I cannot make changes to the any fields including the native fields like First Name, Last Name, etc. If I disable the plugin, I can make changes to the native data.
I disabled all other plugins except for “User Extra Fields” and “WooCommerce”. and the results are the same (still cannot save data).
This kind of issue usually is related to a PHP misconfiguration. More in specific, this issue happens when you have a too low value of the max_input_vars setting. heck the WooCommerce -> Status -> PHP Max Input Vars. Raise it to a value higher of the current one (it usually should be above 12000). To do that, edit your PHP.ini file and set the max_input_vars variable to a value greater than 12000. Once done, restart your server and go in the Status menu and make sure that the change took effect
Regarding the fields editing, from my tests all seems working as expected. I could be missing something. In order to understand if the issue is actually caused by the plugin, please use the following site: https://codecanyondemo.work/wpuef/wp-admin/ (user: demo, pass: demo) to recreate your scenario. Report to me if you are experiencing the issue and how to experience it. Thank you.
I set the max_input_vars=12000; as suggested but it made no difference. I am not able to use the demo site to recreate the scenario because I don’t have access to the My Account page.
I’ve done all the testing I have time for. Please issue me a refund so I can find a different plugin that works.
Lu Myser
Please disregard my previous message. I wish to get this fixed. I don’t want a refund, I want it working
From my tests all work as intended. If you are not able to save, the issue is caused by a server issue, in that case, you need to contact your server maintainer. If even with 12000, try raising that value.
Regarding the demo site, what do you mean that you are not able to access the “my account” page? I’ve double-checked, and using the login data I’ve shared you can access that page: https://nimb.ws/cPzBNw
In order to be sure the issue is not caused by the plugin, please use the demo site so I can perform some further analysis.
I bumped the max_vars to 22000. I disabled all plugins except “User Extra Fields” and “WooCommerce”. I changed the Theme from “DIVI” to “Twenty Twenty-Two”. Without your plugin enabled, I’m able to change and save data. With your plugin, whenever I click save, it get the message “Please fill out all password fields”.
Without your plugin enabled it works fine. I can edit data and save it. With your plugin enabled I says “Please fill out all password fields” when I click save. If I enter a new password in the “New Password” and “Confirm Password” fields, it will store the data when save button is clicked
I’m sorry, could you provide a more detailed description of what you mean by “saving data”? because it seems you were not able to save data when configuring the fields options (admin area).
Please, use the demo site I’ve reported in order to recreate your scenario, so I can see by myself the error you are experiencing and perform some further tests.
P. S.
try updating to the latest 16.4 version. I’ve found that if you were using the “display the extra fields before the original fields” option, WooCommerce was rendering the fields outside the form (so they were not posted and so not saved). The new version addresses that issue.
Is there a private address I can give you to send you all the info and admin login so you can see what is happening on my site?
to see what is happening. This site is in development so no worries about any changes…
Here’s what happens… Go into Account Detail.
If you change anything and click “Save Changes, you get the message “Please fill out all password fields.” and nothing is saved.
If you change the password along with other data then it saves correctly.
All plugins are disabled except woocommerce and user extra fields. Using divi theme. User Extra Fields is version 16.4. Max_Vars set to 22000
I can give you admin access privately if you wish.
Thank you for sharing, but from my tests, all works as expected. I am able to save without any issues. Save button works even if I do not fill the password field: https://www.dropbox.com/s/vyezi85rz6m0xc7/wpuef_save.mp4?dl=0
Please make eventually sure you have purged your browser cache after updating the plugin and that you are using a fully HTML5-compliant browser like Chrome or Firefox.
it works flawlessly with other browsers, but not with Chrome. I uninstalled chrome completely and reinstalled it. It worked ok a couple of times then went back to the same thing. Saying “Please fill out all password fields.” whenever I click to save changes. I googled “Chrome Please fill out all password fields.” and see some things about “autofill” and “novalidate” being an issue with Chrome. If you cannot fix this issue with Chrome, Is there a way I can create the fields under a separate endpoint like “Website Logins” instead of the default “Account Details”. Or can you point me to the file that contains the endpoint that is used by default?
I think if it was in it’s own endpoint, it probably wouldn’t have this issue.
From my tests, all work as expected. It also sounds strange that it works a couple of times. If the page is always the same (same code to run by the browser), the result must be the same. Furthermore, the plugin, by default is not altering password fields. It just adds an extra input field. You can give a look at the woocommerce_my_account.php file you find in the classes\templates folder inside the plugin. that’s the file to add additional fields according to the existing configuration (you won’t find any “novalidate” or “autofill” attribute). Did you enable any option to override the default password option: https://nimb.ws/BOhgEn? Did you perform the test I requested on the demo site? Are you experiencing the same issue?
I’m sorry, but it is not possible to display the fields in another endpoint. Make eventually sure you are not using any Chrome extension that might be interfering. Make also sure you are not using any optimizing/caching plugin that might be the cause of the issue.
Ok… I uninstalled Chrome and Re-Installed it again. Everything worked fine. I logged in and out several times at “https://wp-prosupport.com/my-account” using a demo username and also my admin username. Still worked ok.
Then I logged into my WordPress dashboard “https://wp-prosupport.com/wp-admin”. Once I did that it started failing again with the “Please fill out all password fields” message whenever I tried to save changes on the my-account page.
I cleared browser cache, logged out of my dashboard completely, went directly to my-account with a new instance of Chrome, logged in with the demo username and it still failed.
Somehow logging into the WordPress dashboard as Admin causes the issue. Once I do that, nothing I do seems to fixe the issue except uninstalling and re-installing Chrome. I’m not sure if this is information you can use of not. But that is what is going on.
I’m really sorry, but that issue doesn’t depend on the plugin. It seems more a Chrome issue. I’m really sorry, I cannot provide assistance for that software.
I just discovered… Once I have logged into the WordPress dashboard, then go to my-account with your plugin enabled, the password field is autofilled. If I delete the autofilled password it works. It seems to me that all you would have to do is make sure the password filed does not get autofilled. Or you need to blank it.
If you cannot fix it, please issue a refund.
Anyone who has autofill on with a stored password will have an issue. The issue is that the password field should be blank but it is getting autofilled. Simply blank the field to fix the issue
I tested this with Microsoft Edge and Chrome both. If the autofill prefills the password field it fails.
As mentioned before. With your plugin enabled, the password field is getting populated with the current password. With your plugin disabled, the password is not getting populated.
Thank you for the result of your investigation. That, however, doesn’t depend on the plugin. Chrome recognizes the password field (that is not managed by the plugin) and fills it with the data you stored. That’s the expected behavior of any form. That eventually depends on the “my account” template used by your theme and on your browser settings.
Maybe I have an idea. The fact that a text field is empty, triggers the autofill on Chrome. Try updating the plugin to the latest 16.5 version.
In case any of the extra (text) fields have an empty value, the plugin replaces it with a “” character. It is a workaround to avoid Chrome using its autofill feature.
Thanks for sticking with it, That is definitely a step in the right direction. I can live with it this way.
However, you may want to do a bit more to fix the issue on Chrome and Edge when logged into the admin account. If you want to pursue it further, I’m happy to do more testing and give you the results. Chrome and Edge are working the same. See results below.
On Chrome: - If I login with a demo (customer) account, the password field is now blank and works fine. - If I login with my WordPress admin account, the password field is auto-filled and doesn’t work correctly.
On Microsoft Edge: - If I login with a demo (customer) account, the password field is now blank and works fine. - If I login with my WordPress admin account, the password field is auto-filled and doesn’t work correctly.
On Firefox: - It works ok whether I’m logged in as demo or admin. The password field is not auto
Thanks, Lu Myser WP-ProSupport.com
Thank you for reporting. Unfortunately, this seems a Chrome “bug” and it doesn’t allow 3rd party to disable its autofill feature with any html directive.
For now, doesn’t come anything else apart from the workaround I’ve implemented. I’ll try thinking something but I cannot assure you anything.
It is actually the exact same issue with Chrome and Microsoft Edge browsers. They both do exactly the same thing.
With your plugin enabled, both browsers would auto-fill the password field (but now with your latest version 16.5, only when you are logged into your admin account). They both work ok for customer accounts. I was a coder many years ago but not familiar with PHP. The only thing I could think of is to, as a last step, check the password field and if not blank, null it out.
Anyway, it is at least useable now with your latest version. Thanks again
Yes, unfortunately, seems that whenever the plugin includes an empty field, this will trigger the Chrome autofill function. This is why the password field is filled by the Chrominium engine despite the plugin is not managing that field.
to avoid this, the plugin fills its empty fields with the “” HTML character This issue however doesn’t depend on any PHP code and the browser doesn’t expone any HTML directive to disable that feature.
I’ll perform some further investigation to see if it is possible to implement further workarounds.
Hi I am using the buddypress fields through your plugin. I am using buddyboss. The fields appear in the profile as expected and can be edited although the problem is the fields appear below and outside the border box of the other xprofile fields setup in buddyboss. I want them to appear in the same box. I can send a screenshot if I have an email. Also I can renew my support if you think you can solve this. Thanks!
Hi,
I’m sorry, but I don’t think it can be resolved. Data are injected by hooking to the bp_after_profile_field_content action. If that action is triggered by the page template after the box, there isn’t much I can do.
You should eventually modify the page template and move the action where you wish the fields to be displayed.
Hi This is a bug report I’ve define a field type coutnry_and_state, and wp crash when creating a new user (templates/wp_wccm_my_account.php:62 & 64) Seems this is because you consider setting a value in an array, but field_value at this step is a string (previous init line 43)
Also, not sure this make sense, but there is no support to override templates in theme (eg. templates/wp_wccm_my_account.php). I only try it to debug the crash, this is not a need at this time…
Hi,
Thank you for reporting. Actually, the $field_value variable, when managing the country_and_state field type, should be an array, not a string. Line 38, when invoking the get_field() methods, returns an array. But, when creating a new user, that line stores an empty string that leads to the issue you reported.
I’ve fixed it in the new 16.3 plugin version. The new version allows you to store template files on the “wpuef” directory you can create into your theme folder. I hope you enjoy it!
seems to be ok now. Thanks
Glad to hear that!
At last but not least, I would ask you to help me: If you enjoyed my efforts to assist you and/or my plugin please consider leaving the 5 stars…It would help me with sales, I would really appreciate it!
(to leave a rating: go to your profile page, click on “Downloads” and from there you can rate your purchases.
You can also leave the rating through the plugin description page: https://www.dropbox.com/s/v6zaoe0p6cs4x2o/rating.png?dl=0 )
Have a great day!
Hello, I am having trouble activating User Extra Fields product I just purchased. If states that the purchase code is invalid. I have the License Certificate with the license code
Hello,
please make sure you are using a fully HTML5-compliant browser like Chrome or Firefox. Try eventually disabling the other 3rd party plugins, one of them might be interfering with the activation process.
