Forum Replies Created

Viewing 15 replies - 1 through 15 (of 27 total)
  • Thread Starter christian-s

    (@christian-s)

    Resolved – turns out that I had run out of available disk space on the new hosting solution. So this error was a result of not being able to write more data to the disk.

    Thread Starter christian-s

    (@christian-s)

    Just checked and I got this working with release 3.2.1.
    Solution was to add the wp-cron control secret string as a query argument in backwpup settings.

    thanks for the fast fix to this.

    Thread Starter christian-s

    (@christian-s)

    Thank for the fast response Daniel.
    I’ll look out for rel 2.3.1.

    Thread Starter christian-s

    (@christian-s)

    thanks Matty. Upgrade was successful, I didn’t encounter any problems.

    worked for me to. After upgrade to wp 3.2.1 and link library to 5.0.8 my category listing was messed up. Deactivating and reactivating the plugin solved the issue. Btw I upgraded directtly from within wp admin.

    thanks for great support regarding the
    /* IE */ #fancybox-loading.fancybox-ie div { background: transparent; filter: ...
    on my page. The solution was simply to reset the stylesheet in the plugins settings page.

    I have no idea why the stylesheet all of a sudden included all that stuff.

    The plugin is working for me again as expected.

    Hi Jack,
    Weird. I have tried to delete the plugin via ftp and upload again and I still get this error. Then I tried uninstall from wordpress admin plugin pages and then reinstall again. And I keep getting this weird error.

    Is there a cache somewhere that I should be aware of?

    thanks for the update Jack. I’m still getting errors. Now the page I have link library on states “page not found” (the standard wordpress error for non-existing pages) and then it shows this code

    /* IE */ #fancybox-loading.fancybox-ie div { background: transparent; filter: progid:DXImageTransform.Microsoft.AlphaImageLoader(src='http://www.mysite.com/wp-content/plugins/link-library/fancybox/fancy_loading.png', sizingMethod='scale'); } .fancybox-ie #fancybox-close { background: transparent; filter: progid:DXImageTransform.Microsoft.AlphaImageLoader(src='http://www.mysite.com/wp-content/plugins/link-library/fancybox/fancy_close.png', sizingMethod='scale'); } .fancybox-ie #fancybox-title-over { background: transparent; filter: progid:DXImageTransform.Microsoft.AlphaImageLoader(src='http://www.mysite.com/wp-content/plugins/link-library/fancybox/fancy_title_over.png', sizingMethod='scale'); zoom: 1; } .fancybox-ie #fancybox-title-left { background: transparent; filter: progid:DXImageTransform.Microsoft.AlphaImageLoader(src='http://www.mysite.com/wp-content/plugins/link-library/fancybox/fancy_title_left.png', sizingMethod='scale'); } .fancybox-ie #fancybox-title-main { background: transparent; filter: progid:DXImageTransform.Microsoft.AlphaImageLoader(src='http://www.mysite.com/wp-content/plugins/link-library/fancybox/fancy_title_main.png', sizingMethod='scale'); } .fancybox-ie #fancybox-title-right { background: transparent; filter: progid:DXImageTransform.Microsoft.AlphaImageLoader(src='http://www.mysite.com/wp-content/plugins/link-library/fancybox/fancy_title_right.png', sizingMethod='scale'); } .fancybox-ie #fancybox-left-ico { background: transparent; filter: progid:DXImageTransform.Microsoft.AlphaImageLoader(src='http://www.mysite.com/wp-content/plugins/link-library/fancybox/fancy_nav_left.png', sizingMethod='scale'); } .fancybox-ie #fancybox-right-ico { background: transparent; filter: progid:DXImageTransform.Microsoft.AlphaImageLoader(src='http://www.mysite.com/wp-content/plugins/link-library/fancybox/fancy_nav_right.png', sizingMethod='scale'); } .fancybox-ie .fancy-bg { background: transparent !important; } .fancybox-ie #fancy-bg-n { filter: progid:DXImageTransform.Microsoft.AlphaImageLoader(src='http://www.mysite.com/wp-content/plugins/link-library/fancybox/fancy_shadow_n.png', sizingMethod='scale'); } .fancybox-ie #fancy-bg-ne { filter: progid:DXImageTransform.Microsoft.AlphaImageLoader(src='http://www.mysite.com/wp-content/plugins/link-library/fancybox/fancy_shadow_ne.png', sizingMethod='scale'); } .fancybox-ie #fancy-bg-e { filter: progid:DXImageTransform.Microsoft.AlphaImageLoader(src='http://www.mysite.com/wp-content/plugins/link-library/fancybox/fancy_shadow_e.png', sizingMethod='scale'); } .fancybox-ie #fancy-bg-se { filter: progid:DXImageTransform.Microsoft.AlphaImageLoader(src='http://www.mysite.com/wp-content/plugins/link-library/fancybox/fancy_shadow_se.png', sizingMethod='scale'); } .fancybox-ie #fancy-bg-s { filter: progid:DXImageTransform.Microsoft.AlphaImageLoader(src='http://www.mysite.com/wp-content/plugins/link-library/fancybox/fancy_shadow_s.png', sizingMethod='scale'); } .fancybox-ie #fancy-bg-sw { filter: progid:DXImageTransform.Microsoft.AlphaImageLoader(src='http://www.mysite.com/wp-content/plugins/link-library/fancybox/fancy_shadow_sw.png', sizingMethod='scale'); } .fancybox-ie #fancy-bg-w { filter: progid:DXImageTransform.Microsoft.AlphaImageLoader(src='http://www.mysite.com/wp-content/plugins/link-library/fancybox/fancy_shadow_w.png', sizingMethod='scale'); } .fancybox-ie #fancy-bg-nw { filter: progid:DXImageTransform.Microsoft.AlphaImageLoader(src='http://www.mysite.com/wp-content/plugins/link-library/fancybox/fancy_shadow_nw.png', sizingMethod='scale'); }

    and after that segment the page shows correctly with the link output. The page I have just have these paramaters:
    [link-library-cats settings=1] [link-library settings=1]

    Any ideas what is going wrong?

    I downloaded the 4.2.6 package, unzipped locally and uploaded the link_library via FTP to site and let it overwrite all files as needed. This did not solve the problem for me. Still getting header errors.

    I’m also getting various errors, like
    Warning: Cannot modify header information - headers already sent by (output started at .../public_html/wp-content/plugins/link-library/link-library.php:1) in .../public_html/wp-includes/pluggable.php on line 890

    and when I log off I get a page with

    Warning: Cannot modify header information - headers already sent by (output started at .../public_html/wp-content/plugins/link-library/link-library.php:1) in .../public_html/wp-login.php on line 337
    Warning: Cannot modify header information - headers already sent by (output started at .../public_html/wp-content/plugins/link-library/link-library.php:1) in .../public_html/wp-login.php on line 349
    Warning: Cannot modify header information - headers already sent by (output started at .../public_html/wp-content/plugins/link-library/link-library.php:1) in .../public_html/wp-includes/pluggable.php on line 717
    Warning: Cannot modify header information - headers already sent by (output started at .../public_html/wp-content/plugins/link-library/link-library.php:1) in .../public_html/wp-includes/pluggable.php on line 718
    Warning: Cannot modify header information - headers already sent by (output started at .../public_html/wp-content/plugins/link-library/link-library.php:1) in .../public_html/wp-includes/pluggable.php on line 719
    Warning: Cannot modify header information - headers already sent by (output started at .../public_html/wp-content/plugins/link-library/link-library.php:1) in .../public_html/wp-includes/pluggable.php on line 720
    Warning: Cannot modify header information - headers already sent by (output started at .../public_html/wp-content/plugins/link-library/link-library.php:1) in .../public_html/wp-includes/pluggable.php on line 721
    Warning: Cannot modify header information - headers already sent by (output started at .../public_html/wp-content/plugins/link-library/link-library.php:1) in .../public_html/wp-includes/pluggable.php on line 722
    Warning: Cannot modify header information - headers already sent by (output started at .../public_html/wp-content/plugins/link-library/link-library.php:1) in .../public_html/wp-includes/pluggable.php on line 725
    Warning: Cannot modify header information - headers already sent by (output started at .../public_html/wp-content/plugins/link-library/link-library.php:1) in .../public_html/wp-includes/pluggable.php on line 726
    Warning: Cannot modify header information - headers already sent by (output started at .../public_html/wp-content/plugins/link-library/link-library.php:1) in .../public_html/wp-includes/pluggable.php on line 727
    Warning: Cannot modify header information - headers already sent by (output started at .../public_html/wp-content/plugins/link-library/link-library.php:1) in .../public_html/wp-includes/pluggable.php on line 728
    Warning: Cannot modify header information - headers already sent by (output started at .../public_html/wp-content/plugins/link-library/link-library.php:1) in .../public_html/wp-includes/pluggable.php on line 731
    Warning: Cannot modify header information - headers already sent by (output started at .../public_html/wp-content/plugins/link-library/link-library.php:1) in .../public_html/wp-includes/pluggable.php on line 732
    Warning: Cannot modify header information - headers already sent by (output started at .../public_html/wp-content/plugins/link-library/link-library.php:1) in .../public_html/wp-includes/pluggable.php on line 733
    Warning: Cannot modify header information - headers already sent by (output started at .../public_html/wp-content/plugins/link-library/link-library.php:1) in .../public_html/wp-includes/pluggable.php on line 734
    Warning: Cannot modify header information - headers already sent by (output started at .../public_html/wp-content/plugins/link-library/link-library.php:1) in .../public_html/wp-includes/pluggable.php on line 890

    Thread Starter christian-s

    (@christian-s)

    thanks alchymyth for pointing me in the right direction.

    I now have a child theme working with a few style changes.

    /*
    Theme Name:     Twenty Ten Modification
    Description:    Child theme for the Twenty Ten theme with style minor modifications
    Author:         chr-s
    Template:       twentyten
    Version:        0.1.0
    */
    
    @import url("../twentyten/style.css");
    
    /* Overriding the default heading styles h4, h5 and h6 from Twenty Ten Template */
    
    #content h4,
    #content h5 {
    	font-weight:bold; /* Making the titles bold */
    	color:#3a0675;    /* Making the titles dark blue */
    	font-size:110%;	  /* Increasing the font size */
    }
    
    #content h6 {
    	font-weight:bold; /* Making the titles bold */
    	font-size:100%;	  /* Setting the font size */
    }
    
    #content h7 {
    	font-style:italic;/* Making the titles italic */
    	font-size:100%;	  /* Setting the font size */
    
    }
    
    .hangtext {
        text-indent: -45px;
        padding-left: 45px;
    }

    This way it’s easy to keep track of what changes I’m making to the theme and I don’t need to worry if it will be overwriten next time there is an update to the twenty ten theme.

    Thread Starter christian-s

    (@christian-s)

    Cool. Thanks. I’ll do some testing!
    I did read “HTML Utopia: Designing Without Tables Using CSS” by Dan Shafer years ago. But I seem to have forgotten it all 🙂

    thanks for the help!
    – Chr

    Thread Starter christian-s

    (@christian-s)

    Thanks! Still trying to understand the css logic.

    So if I want to have a few headings available in log posts I could maybe change h4, h5, h6 and see if that would have any unforeseen impacts elsewhere in the site design.

    To make the css specific for blog post should I use the “class” in the csss definition? Like:

    h4#entry-content {
           color:blue
           fontsize:large
    }

    Where is the size of the h1, h2.., h6 defined? I couldn’t find that anywhere in the style.css file.

    Thread Starter christian-s

    (@christian-s)

    I guess there are a zillion configurations out there. I have no idea what the media manager requires, but there could be conflicts with apache, linux, mysql or php (or windows). Each of these are installed at various versions. On top of this, the hosting companies may have their own ways of managing share hosting. Finally the endusers like us may have our own configuration of file permissions, htaccess and php.ini files.

    So I don’t blame WP if it isn’t working or the host for that matter. This is probably more tricky than one would think.

    And how on earth would you test it?

    I like NextGEN gallery for the way that it collects and shows the current settings for php in the dashboard.

    To get Media Manager working always would maybe require some sort of server side settings summary and troubleshooting path suggestions based on the configuration. And if there would be a problem then maybe a standard text that the user could copy/paste to an email and mail to the hosting company.

    Thread Starter christian-s

    (@christian-s)

    Finally gave up trying to get wordpress media manager working on the host after spending the better part of June with various setups, support calls and emails. The solution was to change to a new host. Here everything works fine.

    Took me maybe 2-3 hours to:
    export Mysql db, download files from old server.
    create and import mysql db and upload files at new server
    create similar mail accounts
    check everything was working and then order the DNS change.

    I should have done that a lot earlier and saved me some time.
    My site is now hosted at site5.com.

Viewing 15 replies - 1 through 15 (of 27 total)