csloisel

What I meant was that domain.com/works and domain.com/team are not standard WordPress features, and are probably features of your theme or a plugin.

• This reply was modified 7 years, 7 months ago by csloisel.
• This reply was modified 7 years, 7 months ago by csloisel.

Well it seems you are already using a plugin or a theme that has custom post types or something for those sections since that is not part of default WordPress. It’s really up to the theme/plugin developers if they want to make that editable or not and you should contact them and see if they can assist.

• This reply was modified 7 years, 7 months ago by csloisel.

This appears to be an intentional decision by the plugin directory team. They revised plugin submission guidelines to only allow standard installation plugins. The decision eliminated the need for an installation section in most cases and it was removed/hidden. They later revised it to prepend any installation section in the readme to the FAQs. You can read more here.

• This reply was modified 7 years, 7 months ago by csloisel.

I hate to be blunt but if it only happens with the plugin then it’s probably a plugin issue. That being said, there are cases where plugins are doing everything right and are limited by, or are at the mercy of core functionality ( intentional or otherwise ).

If it is an issue with core someone is going to have to debug the issue and find the specific place in core where it’s breaking and steps to reliably reproduce the issue, then create a ticket in core trac. The bug will have to be reproducible without installing the plugin and probably shouldn’t even mention the plugin or it will likely get brushed off. The best people to do this would be the plugin developers.

Have you tried enabling debug to see if any errors are being thrown?

SoapClient is a class in the SOAP php extension which needs to be enabled on your host. I would contact your hosting company and see if they can install it.

• This reply was modified 7 years, 7 months ago by csloisel.

Was this a one to one migration? Same exact theme, same exact plugins, and everything else?

You could try adding the same function to the archive title filter:

add_filter( 'get_the_archive_title', 'vehicle_listing_title' );

Or modifying the template to call your custom function where you want it to appear.

I would recommend reaching out to the plugin developers/support; they are the most knowledgeable regarding their plugin and the most able to help with any issues.

• This reply was modified 7 years, 7 months ago by csloisel.

Plugin data removal is really at the discretion of the plugin developers. Some remove data automatically when removed or deactivated, some have manual removal methods, some don’t have any method of removal.

However, any lingering data is stored in the database and won’t cause any increase in page file size, maybe some slight disk space usage. At worst it will increase query times on the tables where it stores the data, and it would take a large amount of data to have a noticeable impact.

Plugins also store data with unique identifiers, and most go out of their way to ensure there won’t be any conflict with other plugin data, usually with a unique prefix on the storage keys. In the unlikely event you do notice conflicts with plugin data, I would notify both parties to resolve the issue. And because each plugin data storage is unique it is virtually impossible to have a universal cleanup method; doing so would require cataloging and tracking each piece of data plugins store and how they store it.

I really wouldn’t be concerned with the leftover data, but if you are, I would contact the developers of the plugins in question about how to purge the data.

• This reply was modified 7 years, 7 months ago by csloisel.
• This reply was modified 7 years, 7 months ago by csloisel.
• This reply was modified 7 years, 7 months ago by csloisel.
• This reply was modified 7 years, 7 months ago by csloisel.

Try:

.contact .container .col-md-8.col-sm-8 {
    width: 100%;
}
.contact .container .col-md-4.col-sm-4 {
    display: none;
}

I would contact the plugin authors about how to remove the logged in restriction.

I would start by doing this output in the post type single template. Doing this via a hook is adding an unnecessary layer of complexity here, giving you limited control on placement and is simply not intuitive.

If you don’t have a template already it’s pretty easy to set one up. Just start out by adding a single-suppliers.php into your theme root. Then copy everything from single.php and paste it into the new file. However, you don’t want to do this on a pre-made theme as you won’t be able update it without wiping out your changes. So if you are using a pre-made theme make sure you do this in a child theme.

As for getting multiple fields you want to repeat the get_post_meta() call for each field using a unique variable for storage, it won’t retrieve more than one at a time.

For example:

$office_phone = get_post_meta( get_the_ID(), 'main_office_phone', true );
$contact_person = get_post_meta( get_the_ID(), 'contact_person', true );

Try using the get_field() function I linked above instead of get_post_meta(). I can’t remember how ACF stores fields but it is possible that the method of storage doesn’t map 1:1 in post meta with the exact key you specified in the field.

• This reply was modified 7 years, 8 months ago by csloisel.

Also if you have any particular code that you feel should be working but isn’t for whatever reason, you can post the relevant bits and we can look it over and see if we can figure out what’s going on.