Custom Mini-Profile Creator

[Brian]

Nov 23, 2015 17:14:06 GMT -8 Alan Vende said:

Brian : For some reason, the Custom MP Plugin isn't working on my Samhain, Chakra, New PP, ProBoards Default, or Red Velvet themes. It's the same error message as what was showing before.

I will say that I haven't changed anything in there since you went in and fixed the problem. I'm not sure what problem is going on now, though.

It's working fine on the Chakra theme.

Every other theme you mentioned has the same problem I linked to earlier. You need to remove the line breaks and tabs from the span elements that produce your custom fields in your mini-profile template so that the span opens and closes on the same line.

You can compare the HTML that produces the custom fields on the Chakra theme to those on other themes and see the difference in how they're structured.

[Lynx]

Quick question for you Brian.

In Example 3 (like what you're using above with the "windows" on mouseover), what would be the ideal image size to fit right in that "window" area - where it doesn't extend above the group / rank stars nor below where your Online and Post count is. Just looking for an image size for that area please.

Thanks!

[Brian]

Nov 29, 2015 14:05:58 GMT -8 Lynx said:

Quick question for you Brian .

In Example 3 (like what you're using above with the "windows" on mouseover), what would be the ideal image size to fit right in that "window" area - where it doesn't extend above the group / rank stars nor below where your Online and Post count is. Just looking for an image size for that area please.

Thanks!

The center area that's hidden before hover is 225px in height.

I don't have a width specified but based on the padding of the area around it relative to the full width of the mini-profile I believe the width is 170px.

[Lynx]

Thank you, kind sir!

[Alan Vende]

Nov 24, 2015 9:42:03 GMT -8 Brian said:

Nov 23, 2015 17:14:06 GMT -8 Alan Vende said:

Brian : For some reason, the Custom MP Plugin isn't working on my Samhain, Chakra, New PP, ProBoards Default, or Red Velvet themes. It's the same error message as what was showing before.

I will say that I haven't changed anything in there since you went in and fixed the problem. I'm not sure what problem is going on now, though.

It's working fine on the Chakra theme.

Every other theme you mentioned has the same problem I linked to earlier. You need to remove the line breaks and tabs from the span elements that produce your custom fields in your mini-profile template so that the span opens and closes on the same line.

You can compare the HTML that produces the custom fields on the Chakra theme to those on other themes and see the difference in how they're structured.

Thank you, Brian. Since I want them to be the same on all themes, can't I just copy and paste them? But, at the same time, since it's in the Plugin, why, if it was changed once, isn't it fixed for all of the themes that it's available on? If there's a problem in any plugin and it gets fixed, won't the problem be fixed for all of the themes that the plugin is enabled on?

Sorry if that makes no sense.

[Brian]

Nov 29, 2015 14:37:20 GMT -8 Alan Vende said:

Nov 24, 2015 9:42:03 GMT -8 Brian said:

It's working fine on the Chakra theme.

Every other theme you mentioned has the same problem I linked to earlier. You need to remove the line breaks and tabs from the span elements that produce your custom fields in your mini-profile template so that the span opens and closes on the same line.

You can compare the HTML that produces the custom fields on the Chakra theme to those on other themes and see the difference in how they're structured.

Thank you, Brian . Since I want them to be the same on all themes, can't I just copy and paste them? But, at the same time, since it's in the Plugin, why, if it was changed once, isn't it fixed for all of the themes that it's available on? If there's a problem in any plugin and it gets fixed, won't the problem be fixed for all of the themes that the plugin is enabled on?

Sorry if that makes no sense.

You can, or you can use the Import/Export button at the top to copy them over.

The problem isn't with what's in the plugin but with what's in your themes. The plugin can only work off of what exists on the page you're currently viewing. It does not save the information after you've viewed it once, so the HTML needs to be correct on all of your themes since it has to find that information every time you load a page.

[Alan Vende]

Nov 29, 2015 14:43:37 GMT -8 Brian said:

Nov 29, 2015 14:37:20 GMT -8 Alan Vende said:

Thank you, Brian . Since I want them to be the same on all themes, can't I just copy and paste them? But, at the same time, since it's in the Plugin, why, if it was changed once, isn't it fixed for all of the themes that it's available on? If there's a problem in any plugin and it gets fixed, won't the problem be fixed for all of the themes that the plugin is enabled on?

Sorry if that makes no sense.

You can, or you can use the Import/Export button at the top to copy them over.

The problem isn't with what's in the plugin but with what's in your themes. The plugin can only work off of what exists on the page you're currently viewing. It does not save the information after you've viewed it once, so the HTML needs to be correct on all of your themes since it has to find that information every time you load a page.

Oh! Duh. So you're talking about in the mini-profile template for the theme itself, right? I thought you were talking about the plugin itself when I read what you said. My bad! I've never thought about the import/export buttons. I always thought that those put a copy onto your computer, do they not?

Sorry for completely misinterpreting what you said... again.

The problem is in the mini-profile template of the theme, not of the plugin. The problem is in the mini-profile template of the theme, not of the plugin. The problem is in the mini-profile template of the theme, not of the plugin. The problem is in the mini-profile template of the theme, not of the plugin. The problem is in the mini-profile template of the theme, not of the plugin...

I'm just going to keep repeating that to myself, LOL.

[Alan Vende]

Oh, also, Brian: I'm seeing that the MP variant in the The World of the Paranormal boards is not black; it's blue, like the other variants. It was working before when they others weren't, but now it's not. I haven't changed anything around in there yet, so I'm not sure if it's something I overlooked or is it something to do with the templates?

I think it's something to do with the code, but not the design itself, if that makes sense.

[Brian]

Nov 29, 2015 15:03:36 GMT -8 Alan Vende said:

Oh, also, Brian: I'm seeing that the MP variant in the The World of the Paranormal boards is not black; it's blue, like the other variants. It was working before when they others weren't, but now it's not. I haven't changed anything around in there yet, so I'm not sure if it's something I overlooked or is it something to do with the templates?

I think it's something to do with the code, but not the design itself, if that makes sense.

If it's fine on other themes it's a problem with the theme itself.

If it exhibits the same problem on different themes it's a problem with the code you've added to the plugin.

[Alan Vende]

Nov 29, 2015 15:06:54 GMT -8 Brian said:

Nov 29, 2015 15:03:36 GMT -8 Alan Vende said:

Oh, also, Brian: I'm seeing that the MP variant in the The World of the Paranormal boards is not black; it's blue, like the other variants. It was working before when they others weren't, but now it's not. I haven't changed anything around in there yet, so I'm not sure if it's something I overlooked or is it something to do with the templates?

I think it's something to do with the code, but not the design itself, if that makes sense.

If it's fine on other themes it's a problem with the theme itself.

If it exhibits the same problem on different themes it's a problem with the code you've added to the plugin.

I exported the template to the other themes and it looks as if mine is okay, but it's now saying that the one for Sebesis (Sebesis' Mini-Profile in the plugin itself). I have removed and re-typed the name of the mini-profile into the Plugin and into the Mini-Profile Theme custom profile field and it still gives an error message.

I have exported and imported the mini-profile template to all themes and it still shows the problem with my mini-profile variant. The CSS has the !important declaration... so... why? (Sorry, thinking out loud here).

[Alan Vende]

...Now that I think about it, Brian, I think that the themes still have code in the themes themselves that is the same as the code in the Plugin, so I think that they're fighting each other.

[Brian]

Nov 29, 2015 15:22:39 GMT -8 Alan Vende said:

Nov 29, 2015 15:06:54 GMT -8 Brian said:

If it's fine on other themes it's a problem with the theme itself.

If it exhibits the same problem on different themes it's a problem with the code you've added to the plugin.

I exported the template to the other themes and it looks as if mine is okay, but it's now saying that the one for Sebesis (Sebesis' Mini-Profile in the plugin itself). I have removed and re-typed the name of the mini-profile into the Plugin and into the Mini-Profile Theme custom profile field and it still gives an error message.

I have exported and imported the mini-profile template to all themes and it still shows the problem with my mini-profile variant. The CSS has the !important declaration... so... why? (Sorry, thinking out loud here).

According to the error message they have Sebesis' Mini-Profile Badges specified in the custom field, likely because you've either renamed the field or deleted the original field that they had selected. You'll need to reselect the appropriate mini-profile in the Personal tab of their Edit Profile page.

[Alan Vende]

Nov 29, 2015 15:44:48 GMT -8 Brian said:

Nov 29, 2015 15:22:39 GMT -8 Alan Vende said:

I exported the template to the other themes and it looks as if mine is okay, but it's now saying that the one for Sebesis (Sebesis' Mini-Profile in the plugin itself). I have removed and re-typed the name of the mini-profile into the Plugin and into the Mini-Profile Theme custom profile field and it still gives an error message.

I have exported and imported the mini-profile template to all themes and it still shows the problem with my mini-profile variant. The CSS has the !important declaration... so... why? (Sorry, thinking out loud here).

According to the error message they have Sebesis' Mini-Profile Badges specified in the custom field, likely because you've either renamed the field or deleted the original field that they had selected. You'll need to reselect the appropriate mini-profile in the Personal tab of their Edit Profile page.

That worked. Thanks, Brian! I didn't think to look there. I thought it stayed the same.

[Alan Vende]

Brian: I am looking back in the information about the plugin, and I can't seem to find where it shows how to put custom fields into the mini-profiles. I saw it when I originally put them in there, but for some reason I can't find it now.

The information is in there, right? Or am I going blind?

[Brian]

Nov 29, 2015 16:38:54 GMT -8 Alan Vende said:

Brian : I am looking back in the information about the plugin, and I can't seem to find where it shows how to put custom fields into the mini-profiles. I saw it when I originally put them in there, but for some reason I can't find it now.

The information is in there, right? Or am I going blind?

It's in the User Variables tab of the installation window.

To reference your forum's custom profile fields you can use $[user.customfieldname], substituting "customfieldname" with your custom field's name. You'll need to type the name in all lowercase with no spaces and only use characters A-Z and 0-9.

For example, Mini-Profile Theme becomes $[user.miniprofiletheme]. This will output the value of the custom field. In the case of this example, it'll be the name of the mini-profile theme you've chosen in your profile.

In the Javascript portion of the plugin you'd use the text between the brackets to reference the custom field.