Forum Replies Created

Viewing 10 replies - 1 through 10 (of 10 total)
  • I think I can simplify a *part* of the problem.

    Assuming that you have solved the problem of “how to modify the body tag and add the onload function” then …

    Assuming that you have solved that part for *ALL* pages (for example by editing the header.php file and simply editing the opening body tag) …

    Then you only insert the CSS tagging on the numbers on pages or other places where you want the substitution to happen.

    For example, if you ONLY wanted the substitution to happen on your contact page, then on that contact page where the phone number normally occurs, you insert “<span class=”number”>1-800-123-4567</span>” instead of simply “1-800-123-4567”

    That css span is what causes the google function to rewrite your default number to the google call-tracking number. If you no gotto the css span, then no rewriting will occur, even though the opening body tag has loaded the google function.

    So we can control what pages are modified by editing the content of the pages where we desire the phone numbers to be re-written. But we can load the google function on every page, no problem.

    Thread Starter trakwebster

    (@trakwebster)

    No change today. iThemes security still interferes with Wishlist, my sms-broadcast dashboard, and backup buddy. (Three different sites, 3 different themes, all current wordpress and current plugins. Only commonality is iThemes security.)

    I’m surprised that this has not engendered quite a few comments, and an update from ithemes security folks.

    πŸ™

    — Arthur

    trakwebster

    (@trakwebster)

    Thanks so much both you guys. gdnovey for asking and Kafkaesqui for knowing an answer. I had a need for a simple site. It has a little web application. It’s free but it’s important to me that people sign up. Using this information, if somebody is registered and signed up, then I can make the content of a certain page appear.

    If they’re not logged in, an alternate ‘sorry’ message displays, and requests them to register and log in.

    This bit of trickery uses the ‘Inline PHP’ plugin, so that I can do the trick on only one page, by typing (as html) the following code onto the page. (*The ‘Inline PHP* plugin uses ‘<exec>’ opening and closing tags instead of the usual php open and close tags.)

    <exec>
    global $user_ID;
    if( $user_ID ) {
    echo "<iframe src=\"http://somedomain.com/somepage.php\" name=\"somename\" width=\"520\" height=\"520\">You shouldn't be reading this unless something is dreadfully amiss.</iframe> ";
           }
     else {
    echo "Oops! You must be logged in to view this page!
    If you have an account please log in on the 'Login' page.
    If you don't have a free account yet, please <b>register</b> on the Login page.
    You will be sent a confirmation email, and then when you log in,
    The webapp will appear right here on this page. Thank you!
    ";
              };
    </exec>

    I apologize that the iframe line is so long. I got some garbage when I tried formatting my code prettier. Running in one long line is what seems to work the best.

    When a logged-in viewer views this page, the inline frame is open and through it the visitor sees the web-application, which is actually stored elsewhere as it requires more code than fits nicely on a wordpress page.

    Now I need to find a way to prevent anybody from just reading the page source where the true location is openly stated, and just going to the page where the application really sits. I bet there’s a way; probably it will show up soon.

    I agree that “wrap” would have been immediately clearer (or “container”), but as it is it’s OK, and changing it would probably break some old layouts come next upgrade. The smart thing would be to add a comment making it clear. Depending upon the intelligence of a human is always a mistake; even if the human is yourself, somewhere later in time!
    However, whether it’s called rap or wrap or bigboogaloo, it does no harm being there, and permits several useful CSS layout and coloring ideas to be expressed with tweaks to the stylesheet only. This is a good thing, and it does no harm being there when it’s not being used.

    Hi, michel v,
    Thanks for your original work. It’s grown wings. Always a good sign.
    I have a suggestion for you. On the b2 site, you list your website as cafelog. If your visitor is viewing your page there, your visitor is already on the cafelog site. Why not list your page there as your new weblog at intraordinary.com?
    Just an idea.

    Hi,Sushubh,
    I’d be curious to see michel_v’s current weblog. Where is it?

    Hi, Ryan Peeck,
    So on your “About Me” link on the left (at http://blog.rpeeck.com/) , did you just save a copy of the rendered page, edit the html, throw the file into the same directory as the weblog, and place a link to it?
    Or is this “About Me” page somehow brought up, using the weblog machinery?

    I have read elsewhere that search engines don’t like links such as http://domain.com/blog/index.php?foo=1&bar=2&santa=5. Yet this is a natural and easy way for weblogs to pass links around.
    For this reason, many weblogs offer some option for transforming the links into something like http://domain.com/blog/1992/5/3
    However, I wonder. Is it really true that search engines don’t like those original links? Because if the search engines can handle them, why bother changing things? Does anyone here know for sure and for certain, what is true about this?
    If the search engines can handle the ?foo=1 type of links, then the presence of a link to “archive” on your front page should mean that search engines will penetrate to the depth. (If the human can get there, the spider can get there.)
    However, if search engines really and truly require spoon-feeding, then you’ll need to use your weblog’s “fancy url” or “pretty url” feature. And I’ll bet that search on this forum will turn up how to do that.

    Forum: Fixing WordPress
    In reply to: Target=_BLANK

    Well, one idea. In your subject title you have no quotes. The format should have quotes, like this: target=”_blank”.
    I don’t know if that’s the problem, but if you don’t have quotes, add them as shown and see if it works.

    Forum: Themes and Templates
    In reply to: wp Zen Garden!

    The more you can have a *selection* of standard “skins” which newbies and busies can use, the more you ease newbies and busies into the software.
    The more people you ease into the software, the greater the user base.
    The greater the user base, the greater the number of developers.
    The greater the number of developers, the more features and fun stuff.
    Evabody win, hah!

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