Not signed in ( Sign In)

Categories

Welcome, Guest

Want to take part in these discussions? Sign in if you have an account, or apply for one below

Vanilla 1.1.10 is a product of Lussumo. More Information: Documentation, Community Support.

    •  
      CommentAuthorphpjaguar
    • CommentTimeFeb 28th 2010
     permalink
    I am a complete noob with PHP. I am experienced with (X)HTML and CSS, but that's about it. Please bear with me here...

    I have my blog set as the index page. I want it to look like the rest of my site, but my other pages are static HTML. How can I achieve this? As I said before, I know nothing about PHP, despite my username.

    My blog: http://phpjaguar.110mb.com/index.php
    The static page I want my blog to look like: http://phpjaguar.110mb.com/index.html

    Thank you in advance.
    •  
      CommentAuthorjpneok
    • CommentTimeFeb 28th 2010
     permalink
    Not to pop in uninvited or talk out my butt (I'm sure NWM will correct me here where I'm wrong).

    I left a msg on your site, and as I said there, it isn't general practice to "include" an independent blog setup INTO another document, such as an HTML site - blogs are essentially their own very specific type of complete, pre-fab websites, and especially using php and file locations, you can't just call "index.php" from one location into another page (especially if only HTML), because for a blog to work, it has to use dynamic scripting like PHP and all its internal location and file references generally are local to that script, so dynamically calling IT, via <? include "index.php" ?>, into another page can easily break the extended structure, if one doesn't really work the whole thing through, all the way from start to finish, and honestly, by then, you might as well have just written the whole site in PHP by hand then anyway, as much PHP as you'll have to teach yourself about, in order to go from one step to the next.

    Good luck on it all though, maybe NWM will be able to say "Oh, no, he doesn't know what he's talking about, here is all you need to do!" He's done an awful lot of things that have surprised me, in how he just solves this or that seemingly unassailable problem in an offhand way.
    •  
      CommentAuthorNoWhereMan
    • CommentTimeFeb 28th 2010 edited
     permalink
    you are quite right, jpneok, FP is not intended to be "included", it won't generally work.

    Of course there would be ways to customize it to make it work, but -- I'm sorry -- I'm not going to work on that at the moment.

    My suggestion to phpjaguar is creating a custom theme: it doesn't require higher skills than those he already got: knowing a bit of html and css
    •  
      CommentAuthorphpjaguar
    • CommentTimeFeb 28th 2010
     permalink
    Thanks for your guys' advice. I am looking into making a custom theme... this seems to be what
    I'm looking for. I'll update here once I'm done. Thanks again! :D
    •  
      CommentAuthorStanley
    • CommentTimeFeb 28th 2010
     permalink
    Posted By: phpjaguarI am looking into making a custom theme...


    A couple of tips from someone who's just done that:

    Before you begin find, read, and re-read the wiki mini-guide to theming.

    1) Start off with an existing FP theme which looks like it's going to be easiest for you to adapt to look like your existing site. I think the inove theme is a good starter theme for most people. Your main CSS file will then become your FP theme CSS file, so you should add any other CSS to this. You'll find it much easier to simply go through your existing pages and change all the div names to make sure they match whatever is standard in FP (e.g "head" versus "header" and "foot" versus "footer" etc.). Standardise all of these to whatever FP uses and you're half-way there.

    2) Your custom theme's header.tpl is where you have the opening page DocType declaration. Right before the /head tag I include a file called titlemetacss_fp.php.inc, which is where I add any additional META information (keywords. description etc.), alternate CSS sheets and globally required javascripts (links to .js files and code). I for instance have a mixture of these to control style-switching, a form calendar control and any pop-up windows.

    FlatPress will assign the Title and the main CSS file automatically so, for non-FP pages, I include a near identical script but including these two attributes, and I call the file titlemetacss.php.inc - remember to make sure that the CSS file you point to in this one is your FP theme one, in fact delete your old CSS file so there's no confusion.

    3) Menus - I found it easier to simply implement my own standard set of navigational controls across the whole site, rather than try to get the menu blockparser from FP to create a menu in non-FP pages. So, I just have another single include file (in my case called topnavtabs.php.inc) which I use in ALL pages on my site. This way also allows me to style active tabs and implement sub-menus too, which is a lot easier to do when you do it this way.

    4) Eat lots of chocolate and work all night on it, when it's quiet.