Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • robbychen

    (@robbychen)

    Hi,

    I don’t know much about the compatibility issue for the desktop browsers, but here is the code I added in the first switch statement for the main plugin file (ht-ultimate-favicon.php):

    case '16':
    	echo '<!-- For desktop -->';
    	echo '<link rel="icon" type="image/png" href="' . $value . '">';

    It at least works in Chrome.

    Until the next version of plugin is released (and multisite support is added), I will remain the above code in my copy.

    Also, perhaps I didn’t read the entire plugin source, but it doesn’t seem to use all of the favicon sizes generated by the plugin. For example, it doesn’t use 16 X 16 favicon as mentioned in the code above.

    All in all, I like this plugin.

    Thanks.

    I also would like to know whether the latest version of WordPress can support SQLite. With the advent of Ruby on Rails, SQLite becomes more and more popular. Not only it can store data as a file on the hosting server without additional database server, it also can increase WordPress loading speed as the MySQL server on some hosting providers have performance issue.

    Thanks.

    As far as I know, only older versions of WordPress (2.9) supports this plugin which converts MySQL to SQLite. The “Omague” theme contains HTML5, which I think it’s unsupported by WordPress 2.9. And besides, if this is a newly released theme, it’s probably using the latest WordPress API, which the older version of WordPress will not recognize.

    If anyone thinks my explanation is not enough or not correct, welcome to correct me.

    Thanks.

    Hi, I just installed this plugin today and found the same issue. I looked through the source code and found one “bug” on each of the CSS (wp-slick-slider/css/wpss_styles.css.php) and JS (wp-slick-slider/js/init.js.php) PHP files. The problem is on the first line of code after comment.

    require_once $_SERVER['DOCUMENT_ROOT'] . "/wp-load.php";

    This code is useful for the WordPress which are installed in the root directory (localhost), not for the sub-directory (localhost/blog).

    I tried to use one of the WordPress functions get_bloginfo to get the WordPress installation directory:

    get_bloginfo("url");

    But I think this function is used for the themes, not for the plugins since it cannot find the get_bloginfo function.

    My solution is to use relative path to point to wp-load.php in the WordPress root folder:

    require_once "../../../../wp-load.php";

    Change this with the original line for both files and the plugin will be functional properly.

    I really like this plugin since it allows not only the images as the slideshow, but I think it still needs improvement. For example, I’m having a hard time using this plugin to rearrange the order of the slides.

    Thanks for finding out the problem. I first encountered this issue two weeks ago. I’m using latest WordPress version 2.9.1. I thought it’s just the higher site traffic issue. Since then, this has been recently happened to me. I googled this issue and discovered this thread. It always makes me think that what happens when a regular reader of my blog visited the blog and saw 502 error. Thanks for the tip, dandr69.

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