Jeremy Buller
Forum Replies Created
-
Forum: Plugins
In reply to: [PDF.js Viewer] 404 error when using a pdf file in wordpressI’ve found this plugin useful – thanks for that – and once I ran into this issue I found this support thread useful, as well!
I think a safer fix on line 32 of
pdfjs-viewer.php
would be to changehome_url()
tosite_url()
– this allows for cases where WordPress isn’t installed in the web root directory. This yields the same result as jospBin’s suggestion, but doesn’t require the plugin author to know where WordPress is installed, or users to have to edit this file to get around the 404 errors.So, lines 32 and 33 would end up being:
$siteURL = site_url(); $viewer_base_url= $siteURL."/wp-content/plugins/pdfjs-viewer-shortcode/web/viewer.php";
Hope this is helpful – thanks again for the plugin!
I’m glad to hear it! Good idea, differentiating between user levels using
user_can
.Forum: Alpha/Beta/RC
In reply to: Flyout menus (3.5 RC1/2)I have also experienced this issue, on a fresh (and plugin-free) install, but I thought it was somehow particular to my server, so I marked it as resolved…
I had tested this with RC1 on a couple of friends’ servers (both with different hosts), and the flyouts worked fine… and, since RC2, it has worked fine on my server as well.
Not sure if I can be of any help here, but would be happy to send along an admin login, nacin, if you need it!
I still want to figure this out 100% for my own sake, but it does seem to be a problem with my server, or host, so I’ll mark it as resolved. Thanks again for pointing me in the right direction, Ipstenu.
Adding either of the following:
define('SCRIPT_DEBUG', true);
or
define('CONCATENATE_SCRIPTS', false);
yields the desired result. Thanks for the suggestion, Ipstenu! it’s my understanding that setting the ‘script_debug’ constant causes WP to use the non-minified scripts and styles – is that right?
I’m still not sure how this might only cause problems on my server but not on others… any ideas?
Yoast’s filter is useful for removing all WordPress SEO columns from the Page and Post edit screens, and you can easily show only certain columns per user by logging in and editing screen options.
If you happen to want to set only particular WordPress SEO columns to be displayed across the board – for all users – then here’s some code you can run once from functions.php: https://gist.github.com/4074620
If you’d like to set which WordPress SEO columns are displayed for any users created in the future, you can use this code instead: https://gist.github.com/4074688
It’s not the same as including an option in the plugin, and I’m sure there’s a better way to write this stuff, but it worked for me and I hope it’s helpful to others as well.
I’ve also seen the suggestion to use Codepress Admin Columns to manage these columns, though I haven’t used it. Might make more sense to do that.