Spinland

You did, indeed and the CSS issue I was trying to fix in the first place is now all set. ??

Okay, I think you’ve hit on something esmi, and thank you. That account had something enabled called CloudFlare that sounds like a cache scheme. I just disabled it and refreshed my browser reads of the affected CSS files and started to see the updated versions.

Thanks again, I would not have thought to check there.

No, as I posted above a cache plugin was the first thing I looked for. Nothing. I’m checking now whether my ISP does anything similar, as I don’t know. I use Hostmonster.

Here is the test page URL:

https://www.mvadclub.org/test-page/

I’ve been trying to track down in this theme why the OL lists have the right appearance but UL ones do not. It showed that UL were falling back to reset.css. I added some rules to layout.css right where the UL was correctly firing in order to see whether that fixed it, and the new rules never showed up in Inspect Element, which alerted me to this weirdness going on.

I don’t know that it would help, but the site is mvadclub.org. The stuff I’m trying is on an unpublished test page.

I just navigated to the CSS file I uploaded in my browser, and the changes do not show up in the browser. But, if i download that same file to my desktop and open it in a text editor, the changes are there.

The file I looked at in my browser is here:
https://www.mvadclub.org/wp-content/themes/prospect/css/reset.css

It should show a /*************/ line right above the ol, ul, li settings on line 11. If I download that file, the line is there.

The permissions seem fine, I checked and I have write permissions to the directory an to the files, and since the file I downloaded contains the changes it obviously was uploaded. How can it not be reading the correct file when I navigate to it?

Some progress, but a new problem. Through more searching I found this bit of code that works better in that it doesn’t crash the web page or return an empty string:

$datetime = strtotime($post['post_date']);
           $mysqldate = date("Y-m-d H:i:s", $datetime);

The issue now is I pull several posts from the blog with wp.getPosts and in every case the final $mysqldate string from the above code resolves to:

1969-12-31 19:00:00

Either $post[‘post_date’] is not being returned in the xmlrpc call, or something in how I’m trying to format the data to be useful is not working. I’m successfully pulling other data out of the blog, like link and title and content, so I know the basic xmlrpc operations I’m doing are sound.

Does anyone have any ideas?

Thanks in advance!

Okay, so looking into the code, that function appears to be in the WordPress includes folder. The problem is, this is not a WordPress site I’m pulling the posts into–that’s why I’m using xmlrpc in the first place. WordPress-specific code is not available.

So, is there a function (or functions) that can process this datetime data type that exist in the standard PHP libraries?

Thanks in advance!

Thanks, but I when I try to use that function I get:

Fatal error: Call to undefined function mysql2date() in /home2/spinland/public_html/drupal7/modules/php/php.module(80) : eval()’d code on line 35

Okay, I figured it out. For the optional parameters wp.getPosts wants a struct. I was just passing it an integer in $NUMPOSTS. Assigning the number of posts that I wanted in this manner fixed the error:

$NUMPOSTS->number = "20";

Hopefully this helps someone.

That was the clue I needed; got it sorted, thanks!

I have:

https://spinrants.spinland.biz

in both.

Okay, just in case anyone is interested the issue has been resolved, though not via PHP include. The proper method for XHTML Strict compliance should be via the <object> tag, Microsoft’s failure properly to implement that notwithstanding. There is a workaround. Your blog must lie on the same server as the web site itself. In the case of the following example it’s installed into a folder off the web site’s root called my_blog_folder.

<!--[if IE]>
    <object classid="clsid:25336920-03F9-11CF-8FD0-00AA00686F13" type="text/html"
        data="my_blog_folder/index.php" style="width:100%;height:100%;">
        <p>Fallback text</p>
    </object>
 <![endif]-->
 <!--[if !IE]><-->
    <object type="text/html" data="my_blog_folder/index.php" style="width:100%;height:100%;">
        <p>Fallback text</p>
    </object>
<!--><![endif]-->

Enclose this in a <div> tag styled to the size of the block you want the blog to appear in, and it will give you scroll bars if the blog’s larger than the <div> size.

Now I can bring the blog in and satisfy the XHTML Strict standard, for whatever that’s worth.

Thanks for looking.

Because the existing site is generated by a WYSIWYG application and has a set style and design. The blog itself is using a very simple theme and is currently fed into a <div> block on the page using an iframe, but I want to transition the site from XHTML Transitional to Strict and that means ditching iframes. It would also be nice if the actual blog text were served as part of the page so search engines could find it.

I’ve tried replacing the iframe with an <object> tag, which one would think is the proper way to do it, but that bombs on Internet Explorer and apparently there’s no way to make it work (I’ve tried numerous “fixes” I’ve found via Google and though they all work in Firefox none work at all in IE). I was hoping there were some way simply to call the WP code in a similar fashion as iframes but that was Strict compliant.

Now I’m starting to believe it just cant be done. All hail Microsoft.