After updating to Premium I entered some Custom CSS for Google Maps. This caused my Simply Staff plugin pages to display wrong. I then deleted out all the Custom CSS code and the pages still displayed wrong. The only way I can get them to display properly is by restoring Public_Html & the database Not sure how this all interacts.. Currently it is displaying properly. The problem at the Issue URL was that the text would be displaying under the contact pictures.
Origami Premium Upgrade/Custom CSS Problem
This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.
Hi Paul
Sorry to hear about this hassle. This is something you could consider taking up with the plugin author. You could also try re-installing the plugin, that shouldn’t cause any data loss.
Right now the plugin isn’t applying any styling to the bio paragraph. You can try the following under Appearance > Custom CSS:
.staff-member-bio { width: 100%; }The plug-in has it’s own custom css area. Should I add the styling there ?
Actually I just verified the problem is after updating from 1.6.2 to 2.6.1.
It’s up to you. You can add it to the theme or plugins’ Custom CSS area.
I added it to the theme CSS. The problem appears when I update the from 1.6.2 to 2.6.1. Is that a theme or plug-in issue ?
I’m unfortunately not sure what’s up there. The plugin isn’t targeting the bio paragraph at all from what I can see. That looks like a plugin issue. There is no CSS there to handle the bio paragraph.
Remove the previous CSS I sent and insert this instead:
.staff-member-listing .staff-member-bio { float: left; margin-top: 15px; width: 100%; }That causes the bio to appear below so I deleted it.
In your original post you mentioned:
“The problem at the Issue URL was that the text would be displaying under the contact pictures.”
Please let me know where you’d like the text displayed and we’ll assist.
How it is currently displaying. Scroll down this page for a better example:
http://saintpatrickfw.com/former-pastors/
Sorry, I’m still not with you. To confirm.
This page is correct:
http://saintpatrickfw.com/former-pastors/
And you want this page:
http://saintpatrickfw.com/contacts/
To have the same formatting as the first one?
Is the above correct?
I don’t see any difference between the two. Father Thomas E. Doriot for example, the bio text there is the same as the bio text here: http://saintpatrickfw.com/contacts/.
Sorry for the confusion. Both pages are displaying correctly right now. When I used your CSS the bio dropped below the pictures and when I update the Origami theme from 1.6.2 to 2.6.1 the bio drops below the pictures.
Super, I’m with you now. I’d unfortunately need to see what’s happening when things are broken in order to try resolve.
Do you want me to break it ? I can restore after from backup if need be.
I’m online for another 20mins or so. There isn’t really anything we can do to help the styling of that plugin if we can’t see where things are going wrong so yes, you’d need to run the premium upgrade. Thanks.
Updated theme and pages are now broke.
After the update only the Staff List plugin custom CSS is loading. The stylesheet from the plugin itself is not being loaded. We’d need to fix this. It’s not viable to re-write all those styles. Head to Plugins and check that the plugin is still active and working correctly. If the setup is exactly the same then it might be worth deleting the re-installing the plugin. All data should be safe during this process.
How do I delete the plug-in ?
Head to Plugins, de-activate the plugin the plugin in question, then delete it. Those links will be available on the Plugins page.
I received a warning that data would be deleted when I attempted to delete the plug-in , so I backed off. When I re-activated the plug-in the pages began displaying properly. So could it be that the de-activating/re-activating process fixed things ?
Awesome, perhaps changing themes which is essentially what the upgrade is, threw things off in that plugin. Yes, it’s possible that de-activating and activating resolved it. Glad to hear there was progress there.