Forum Replies Created

Viewing 10 replies - 16 through 25 (of 25 total)
  • tell us, and maybe we can tell you exactly how to do it.
    I would be glad to.
    G.Smith

    PS
    in all your rambling, you said “so it can just go to the main page,” ???

    so, just what is it that you want to accomplish?

    sorry, but, you are doing dumb things, and asking for help with some error and not telling us what you did – because you don’t even realize the consequences of what you did.

    you say you created an index.html. Clearly you think writing an html page will replace a server-side program that builds a page dynamically depending on (prior) events. (like did they type in a valid password? are they already logged on, and now, want to log out? Did they forget their password?) … html “has no clue”!

    rusty @ coding“?!
    You are rusty at the html document markup language; you have not learned enough about how to use css. Experts at website design – xhtml and css – are designers, not programmers. Get a current book strictly on css and learn to do it right.
    You are NOT a programmer. php is a server-side programminng language. Get a book on php and MySQL and learn computer programming and about the SQL database language — and leave the php programs alone till you have learned.

    put back the original login.php program and leave it alone.

    you need to state exactly what it is you want to accomplish, not “how”, “what”.

    Sorry, pointing to those other web sites does not explain anything.

    when you upgrade, wp has to upgrade the db. sounds like that has not happened.
    copy in your original, old version, files etc. unpack the 2.8.1 files again and go through the steps of upgrading again “according to the directions” … it’s worth a shot. and may save you a lot of hassles.

    have you already gone into wp-admin/css/login.css
    and put your own header image at the top …
    #backtoblog a {
    background: url(../../images/header.jpg) no-repeat top center;
    font-size: 36px; /* some bigger size !? */
    width: 1000px; /* whatever your */
    height: 170px; /* image size is */

    and removed the wp image …

    h1 a {
    /* background: url(../whatever-it-was); */

    Unless you don’t care about google and the other search engines logging/ranking the content of your site, it is better, according to google, stay with the default permalink:
    “Providing search engines with dynamic URLs should be favored over hiding parameters to make them look static.”
    the default permalink (example: …/?p=123) “should be favored”
    All the other peralink options are static.

    Google has an entire page on the subject:
    http://googlewebmastercentral.blogspot.com/2008/09/dynamic-urls-vs-static-urls.html

    If following google’s advice means your icons will show up, and make search engines happy, then it is a win-win for both you and google.

    Otherwise, did <?php bloginfo(‘stylesheet_directory’); ?> help?

    you don’t mention checking your config.php file. If your db name, user, & pw are all still the same, good.
    Additionally, is the name of your website still the same? and the folder wp is in? … do you maintain a backup / test copy on another server-website?
    Some versions back, it became possible to

    override the database by putting the 2 lines below into your config.php file. – Much easier:

    define(‘WP_SITEURL’, ‘http://&#8217;.$_SERVER[“SERVER_NAME”].’/wordpress’ );
    define(‘WP_HOME’, ‘http://&#8217;.$_SERVER[“SERVER_NAME”].’/wordpress’ );

    change the folder name “/wordpress” to whatever you renamed it to, if you did.

    This way, it is dynamic, and portable, not “hard coded” and “unmoveable”. If you have a backup copy in a different folder, (say one is in wordpress and the other is in backup or testing), using these 2 lines, instead, makes the folder name dynamic also:

    define(‘WP_SITEURL’, ‘http://&#8217;.$_SERVER[“SERVER_NAME”].dirname($_SERVER[‘PHP_SELF’]) );

    define(‘WP_HOME’, ‘http://&#8217;.$_SERVER[“SERVER_NAME”].dirname($_SERVER[‘PHP_SELF’]) );

    This way, your config.php file can be portable along with all the other files. It can be very valuable to not have to maintain multiple config files.

    ggsmith

    (@ggsmith)

    what is needed, is to do regular backups, not making redundant copies.
    it appears that adding 2 lines to the wp-config.php file can work.
    setting the autosave interval to 0 does not turn it off – it goes ‘bonkers’
    but, of course setting it to 100 minutes (6000 sec.) or whatever will do. set it to 200 (12000) if you wish.

    define(‘AUTOSAVE_INTERVAL’, 6000 );
    define(‘WP_POST_REVISIONS’, 0 );

    setting wp post revisions to zero does work. or at least, it did for me.
    if not, it can be changed from true to false in the wp-settings.php file down around line 495 (in ver2.7.1) and, that works. in any case, keep a record of your changes so you can re-implement them with the next upgrade(s)

Viewing 10 replies - 16 through 25 (of 25 total)