Forum Replies Created

Viewing 9 replies - 1 through 9 (of 9 total)
  • I had exactly the same problem after upgrading to 2.0.1 just now. Thanks for doing the sleuth work, andrewfitz!

    If I’m reading the code correctly, that block applies only when there is a record (transient) that you’ve just upgraded or activated the plugin. So deleting the entire block should pose no problems to long-term use (and it’ll get overwritten during the next regular upgrade anyway).

    I’ve no idea why the transient isn’t removed, but I don’t have time to comb through the code to find the proper fix; hopefully itthinx will get it sorted out shortly. In the meantime, it works fine on my WP 4.7.2 with just that block deleted.

    In case anyone else runs into this and isn’t terribly familiar with the folder structure, here’s where I found that code bit to remove:
    website-root/wp-content/plugins/groups/lib/admin/class-groups-admin-welcome.php. I just snipped everything inside the “public static function admin_init() { }” function and left the empty curly braces as a stub function.

    A 1-star is very, very harsh and I must agree with Renee and Emily on this one. One star implies that either the plug-in is harmful or totally fails in its intended function. It’s a warning to other users to stay away from this product.

    Now, anyone who doesn’t read the description of the plug-in before installing it and is then dissatisfied is not justified in complaining via the rating system. In the description for his plug-in, Renee clearly and obviously states:

    Note: This plugin is not able to push back your changes to the live site at the moment! This is a feature i am already working on.

    If you missed that super-obvious warning, shame on you. For issuing a rating of one star, which implies a totally dysfunctional or harmful plug-in, shame on you again. For issuing an unfair rating that has potential to damage a developer’s reputation while simultaneously asking for that developer’s free support shame again. This is very unfriendly behavior.

    This is an open community and the plug-in Renee developed is released for free. He clearly describes what it does and warns about what it cannot do. Mark and Robin, that warning has been there for months, by the way; it’s not a recent addition. (You can verify this at the thread https://wordpress.org/support/topic/staging-to-live-instructions-please?replies=21). Renee actively and helpfully supports his product, to the extent of providing assistance directly to those trying to use it in a full staging manner (who have already tried, have run into trouble, and ask politely for help). He’s an outstanding example of a great WordPress developer and community member.

    Asking for a new feature, asking for support with an existing product, and providing a critical review are all acceptable behaviors here. But bashing a product and a developer because you didn’t do your homework isn’t.

    Thread Starter matthewm

    (@matthewm)

    Never mind. I figured it out with the assistance of a friend. He was able to log in on his computer, even using the same account, and get to the customization just fine. So I cleared the cache on my browser and restarted it, then I was able to get in without any further problem.

    This thread can be closed.

    Thread Starter matthewm

    (@matthewm)

    The default text Simple Tooltips inserts is:

    [simple_tooltip content='This is the content for the tooltip bubble']This triggers the tooltip[/simple_tooltip]

    So, when I changed the single quotes around the “content” parameter, it worked fine. With a single quote, it wouldn’t work at all (in custom post types). No clue why, but it’s an easy fix. Just change the boilerplate to include your tip text surrounded by double quotes:

    [simple_tooltip content="my secret tip"]This triggers the tooltip[/simple_tooltip]

    Thread Starter matthewm

    (@matthewm)

    Update: don’t worry about it. I discovered that the boilerplate text the plug-in uses has single-quotes and if I change those to double-quotes, it all works just fine.

    Thread Starter matthewm

    (@matthewm)

    OK, finally found what I was looking for. The function is, simply, is_home(). Or if you’re using a static front page, you can use is_page(‘Home’). More details at this post:

    http://wordpress.org/support/topic/check-if-page-is-the-main-page-static-front-page?replies=6

    Thread Starter matthewm

    (@matthewm)

    Thanks, leejosepho. Unfortunately, most of the updates are done by non-technical folks who break out in a rash when I mention words in caps like FTP. πŸ˜‰ I’ll check if that’ll work for me for immediate updates, but I’m still very interested in any other suggestions that might lead to a more comprehensive solution.

    Thank you again for your reply,
    -Matthew

    Thread Starter matthewm

    (@matthewm)

    Update – the if/elseif/else problem was definitely a coding error – I’ve gotten that working fine now. Unfortunately, it doesn’t address the issue! I assumed if I could have an “else” case in there, it would apply to the ‘home’ page (the blog posts page) but it doesn’t work!

    Here’s a snippet from the current header.php, showing the last elseif and the final else, which works great on all the static pages but fails on the /news-events/ root or ‘home’ page:

    ...
    elseif (($paget)=="employment"){ echo ('<title>Job Employment Opportunities | Riverstone International School Boise, ID USA</title><meta name="description" content="Learn about job employment opportunities at Riverstone International School in Boise, ID."><meta name="keywords" content="job, jobs, employment, career, careers">'); }
    else { echo ('<title>Updates & Announcements | Riverstone International School Boise, ID USA</title><meta name="description" content="Read about updates and announcements at Riverstone International School in Boise, ID USA."><meta name="keywords" content="updates, announcements, news, events">'); }
    
    endif;
    ...

    There is another similar section in header.php, after the universal stuff I already extracted from these page-specific IF trees.

    <sigh> Still puzzled; more than ever, in fact.

    Thread Starter matthewm

    (@matthewm)

    Thank you so much for your assistance, esmi!

    I tried the if/elseif/else block, as well as a case/switch block, but either had some mis-coded line or another problem, because every time I tried I got a completely blank page. I reverted it back to the original if tree.

    Anyway, I think the problem lies elsewhere, because:

    1. First thing I tried was to extract the common code out of the blocks in the if tree in the header.php. Then I viewed the ‘home’ blog page (http://www.riverstoneschool.org/news-admin/) – the formatting related to the parts I extracted appeared but because the rest of the header formatting was still missing, it is still rather borked.
    2. Next, I tried switching Settings->Reading from “Your Latest Posts” to “Static Page” and setting the Posts page to a subpage formatted the way I want the ‘home’ to look (http://www.riverstoneschool.org/news-events/updates-announcements/). Result: that subpage page then appeared borked exactly as was the ‘home’ page.
    3. Next, tried adding a “is_home()” section to the if tree in header.php, with no change in results.
    4. Switching it back to using ‘Your Latest Posts’ fixes the updates-annoucements page, but I’m again left without a page showing the posts which I can also format with our site’s CSS, Header, and Footer.

    I’m confused about all this, so if my explanation needs clarification, just let me know! πŸ™‚ As always, your tips will be appreciated!

Viewing 9 replies - 1 through 9 (of 9 total)