NinjaDoll_

I figured it out. Works well now.

Bear with me, please, it’s been a long time since I’ve had to customize this plugin, it’s usually worked as intended from the get-go.

The theme is grabbing an h3 page title because that’s what the theme is set to do. This isn’t needed with your plugin, because you already call an h1 inside the page’s content. Eliminating it in the theme means I lose all the titles to all my pages/posts and that’s no good :/

The ID:0 is =somewhere= but I can’t find a way to point the theme to the actual event title rather than to it. I think it may be a WordPress issue, because the event ID isn’t a page ID, so WordPress doesn’t know where to look. I suppose I could theme my single pages “if content is Event, h3.page.title=hidden?” But I’d need to find the plugin data to retrieve to test this. Any suggestion you have would be appreciated, it’s driving me nuts.

Mahalo!

This has not been resolved with the new version. The error continues to pop up, and I already have my app/site approved and live with Facebook. The plugin has also broken the rest of my theme since it’s the 2nd page to load (parallax home page), nothing after it will load. Not sure where to go next other than trying a different plugin, so please check. I like this one a lot :/

Editing the plugin code seems to be the way to go. Thank you for the info! You can close this ticket now, appreciate your help.

Aha! Thanks for clarifying…now that I have it working, the only question is the output location. It’s showing up at the end of the footer, when I’d like it to show above the SUBMIT button. I expect I need to style this to be called inside Appointments+ somewhere.

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

I’m pretty sure I’m writing this wrong because it isn’t working, but I prefer to put it in the functions.php and have written:

<?php
function do_disclaimer() {
    <script type="text/javascript" src="/scripts/do_disclaimer.js">
    add_action( 'wp_footer', 'do_disclaimer' );
    var dropdown = document.getElementById("app_select_services");
        var selectedText = dropdown.options[dropdown.selectedIndex].text;
        if (selectedText.includes("Interview")) {
            document.getElementsByClassName('Interview')[0].style.visibility = 'visible';
        else if (selectedText.includes("Stage")) {
            document.getElementsByClassName('Stage')[0].style.visibility = 'visible';
        else if (selectedText.includes("Audition")) {
            document.getElementsByClassName('Audition')[0].style.visibility = 'visible';
        else if (selectedText.includes("Performance")) {
            document.getElementsByClassName('Performance')[0].style.visibility = 'visible';
        }
    </script>
    }
  <div class="Interview"> <php_e('display this text') ?> ;
  <div class="Stage"> <php_e('display this text') ?> ;
  <div class="Audition"> <php_e('display this text') ?> ;
  <div class="Performance"> <php_e('display this text') ?> ;
}
?>

• This reply was modified 7 years, 10 months ago by NinjaDoll_. Reason: Styling

Kasia, thank you, appreciate your taking the time to provide that snippet. Might do the trick…I will give it a go!

Hi there!

I did as you said, changed Global Width to “0” and it now works perfectly. For the wrapping text, I had to also change Ticker Mode width to “0” and now nothing is cut off, the full text shows. This seems different than in the past but I won’t question it, I’m happy it’s working!

Now if I can figure out how to show all the tickers from the header php function, I’d be happy, but that’s a different issue.

Thank you so much!

I can confirm that the memory limit fix works. I have the Pro version and it stymied my admin abilities until I increased my memory from 256M to 512M. After doing this in php.ini (I used the File Manager in my CPanel) and doing a refresh, admin worked just fine.

Thanks, John!

I’d like to hide it on the entire site, but the home page is a good start. I can probably figure it out from there.

Thank you for the code, it works =)

After a few days of looking, I got a clue from this post from 3 years ago: this thread.

1. I restored the user_roles in the **_2_options table from a different child site. This allowed me to add user_roles, which I found had evaporated along with the plugin issue.

Then I deleted entries in the **_users table of the main install, all of them except Admin.

2. Deactivated all the plugins, added users back with each reactivation, and found the plugin throwing up the bad stuff for site-specific activation was a conflict between TinyMCE Advanced and Black Studio MCE.

So while the plugin I deleted did cause some damage that was easily repaired, the issue about activating plugins on child #2 actually was a good ol’fashioned conflict when the network activated TinyMCE while I had the other one active on the child site.

Thanks for your help! Led me in the right direction and I didn’t have to redo the site!

I have a secondary site that I can transfer to and check it. Database is backed up so I’m good to go that way, thank you for the suggestion. It’s a shame I can’t find the artifact just by looking in the database entries, and an even bigger shame if I have to rebuild most of the site simply to allow it to activate its own plugins. BUT…lessons learned everywhere, right?

Weird, though, that it only affected the one site. I would’ve thought I’d have issues at the network admin level (where I deleted it) rather than just one child site out of several (where I deactivated it).

Sorry, I don’t recall the exact name but it was a front-end user login. It worked fine but was too cumbersome for the client’s needs. Once I deactivated and uninstalled it, child site #2 refused to activate its own plugins. Any plugins. And it was the only site using the user login plugin.

If the problem exists with only that one child site, I haven’t a clue how to fix it in multisite :/ I’ve rolled through WP and the plugin directories for weird code and checked SQL for any artifacts from the plugin but so far I’ve found nothing.

I got it working!

Curtiss, you’ll be so proud of me…I found the issue with the mosaic. Up to you if you want to code a fail-safe into the plugin, but here you go:

One of the widget contents (a contact form) was a table that didn’t end with </table>, it ended with <table>. In essence, it pulled widgets from descendant Collapsible areas in a “continuation” inside the area where the error started.

In this instance, area 4 was collecting collapsible widget data from areas 5 and 6. Since I only have 6 areas, I’m assuming this means Collapsible could take that kind of error and accumulate everything beyond it into a new, messy widget inside itself.

Once I corrected the </table> mistake in the contact form, area 4 was fine. So this is all on me, not the plugin.

But the weird thing is, even though it was collecting tabs from areas 5 and 6, it was reassigning random body parts of the page on which area 4 lived. So the tab in area 6 that said “Saturday” came over, for instance, and made itself call up a footer. That part…I can’t fix, LOL!

Thanks much!