VisualData

Hi there,

Have you found a solution yet? Editing of user profiles at front-end is not an easy task and needs some knowledge about php and html. Are you comfortable with some php code? if not, you may need a developer to help you with this.

What plugin are you using that creates the custom fields? If you have access to phpmyadmin, you can find out the name of the custom fields from the database table, and how the data are stored. The name of custom fields are usually stored in a table called wp_usermeta, in the column called meta_key. if you have changed the table prefix during installation, the table name will be your prefix followed by usermeta. you can search by user_id and see what custom fields are there.

if the data is stored in wp_usermeta table as plain text and numbers the same way as it was entered, you can create a page at the front-end for users to edit profile using the following approach.

here are the steps involved.

1. install and activate a plugin called pods,

2. in pods admin panel, extend the existing content type User, use default meta storage, and create custom fields with the same name as the custom fields created by your plugin.

3. create a page template in your theme folder. if your page slug is edit-profile, your page template needs to be named page-edit-profile.php.

4. you need to use an if statement to check the user login status and retrieve their user id, and wrap the code to output the edit form.

5. you may use an array to specify what fields to show in the form, and use the “form” function to output an eidt form. Please refer to the documentation on pods.io website for detailed instruction about how to use the “form” function. there is a short code for pods form but you still need to check user login status as mentioned in the above step.

in this approach we use pods to retrieve custom fields data from user meta table, update it, so that the other plugin can use the same data later.

This approach will not work if the other plugin stores data in an encoded format. It is still possible but some development work will be required.

please let me know if it works for you.

Oliver

you may need to provide more details about your code for people to help you. the array and forms produced are not enough to tell why the import fails.

I solved a similar problem using wp all import and pods, and have actually coded a custom fields importer plugin for this. image can be imported in one custom field, and displayed in custom post by reading the value from the image custom field. the premium version can handle images.

these are just pages. WordPress stores parent/child relationship in the table posts. with WordPress you don’t need to create a site tree beforehand. when you create pages, if you choose a parent page from the existing page, the relationship will be created for you, WordPress is much easier to use.

Hi,

you may use a plugin to create custom fields for posts and store the extra information in the custom fields. My favourite one is pods as it is easy, flexible and powerful without much coding . Custom fields can be displayed using pods template which can be configured in admin backend .

I hope it helps.

interestingly, I have been thinking of writing a plugin to import some data from a separate mysql table into TablePress table for a better user interface. TablePress is great to present data as a table.

it is not uncommon for popular wordpress websites to have thousands or more posts. Posts are handled efficiently, even with taxonomy.

I use pods to manage more records without taxonomy (the records don’t really need taxonomy), and use relationship fields to drill down and filter these records and show a list of relevant records, similar to how taxonomy works. there are some tricks in running an optimised query with relationship fields. pods is able to handle thousands of records with ease. if you use many custom fields, you may consider table storage to reduce the number of joining queries.

Hi Jamie,

You are welcome. Pods is quite unique in handling bi-directional multi select relationship fields. and it is possible to create very neat user interface to achieve complicated tasks with a few clicks. You will love it once you know how to use it. It is a powerful framework with extensive documentation. I use pods in my own projects, and have coded a custom fields importer add-on plugin to handle data import to pods efficiently since one didn’t exist.

here is a comparison of custom fields plugins.

for the project I have done similar to yours, I created custom post type for each company, and use relationship fields to associate it with authorised users and ordinary users. a company may have a few admin users, and an admin user may manage a few related companies.

if you allow users to submit contents, then all the contents they create can be associated with the company so company admin can have access to these records, but not the records of other companies.

cheers.

Oliver

3000 records should not be an issue for modern servers. however 3000 pages can be overwhelming for users to navigate. have you thought about storing some of the records as a custom post type with custom taxonomy?