Forum Replies Created

Viewing 15 replies - 166 through 180 (of 193 total)
  • Weird. Just a few quick questions: Do you have any other plugins installed? What version of WordPress are you using? And are you using the most recent version of WP Document Revisions?

    Very strange. I would say this might be a permalinks related issue, but the fact that you can download files that end in .doc but not .docx seems a bit odd…

    Sorry for all the questions, but the more info the better chance there is of figuring this out. Do you have the most recent version of WP Document Revisions? Are you using the WP Document Revisions ‘document_extension’ filter in any way? Did you change the WP permalinks recently? Do you have any other plugins (seo especially) installed?

    Would you be able to post back here with what version of WordPress, WP Document Revisions and browser you we’re using when it happened (and if possible, what sort of stack you’re on)? It would be very helpful in trying to figure out what’s going on.

    I have been unable to recreate this issue in the following scenarios, using Google Chrome, Firefox, Safari, IE9, IE8, and Google Docs (to create and save files in .xlsx and .docx), WP 3.5.1, :

    Scenario 1:
    1. Create and save a document (file.docx) in Google Docs in .docx format
    2. In WordPress, create a new document
    3. Upload file.docx to WordPress
    4. Download file.docx from the backend by clicking the “download” link
    5. Download file.docx after being inserted in a published post
    6. File correctly displays the .docx file format without the addition of .doc

    Scenario 2:
    1. Create and save a document (file.xlsx) in Google Docs in .xlsx format
    2. In WordPress, create a new document
    3. Upload file.xlsx to WordPress
    4. Download file.xlsx from the backend by clicking the “download” link
    5. Download file.xlsx after being inserted in a published post
    6. File correctly displays the .xlsx file format without the addition of .xls

    Maybe IE 7 is the issue? If anyone is still encountering this issue and could give some more information on what version of WordPress, WP Document Revisions, and what browser they’re using, that would great.

    I would check out the following filter:
    https://github.com/benbalter/WP-Document-Revisions/blob/master/wp-document-revisions.php#L749

    If you return false, it should force a “save-as” instead of opening in the browser.

    Try using the global $wpdr class.

    So let’s say I did:
    $posts = get_posts ( array( 'post_type' => 'document' ) );

    And it returned an array with one document in it, I could do:
    $wpdr->get_file_type( $posts[0] );

    And that would return the file type of that post. Feel free to post back here if you’re still having issues implementing it.

    Having some difficulty recreating this. I’ve done the following, in order:

    1. Uploaded a document.
    2. Published the document
    3. Create a new post
    4. Added [documents] to the post
    5. Published the post
    6. Checked out the post on the front end
    7. Clicked a document listed in the post body
    8. The document then downloaded

    Is there something you’re doing differently?

    I don’t have a WAMP environment set up at the moment, but I can do so in a few. Do you have anymore information on this issue before I get around to it? Is it giving you any sort of error? Do you have an odd WAMP setup (something very non-standard, etc.)?

    Howdy,
    I opened an issue on GitHub to help fix this: https://github.com/benbalter/WP-Document-Revisions/issues/55

    I don’t have a ton of CoffeeScript knowledge, but I’ll work on trying to fix this issue asap.

    There might be an easier way to do this that Daniel could point to, but off the top of my head I would probably start with the following:

    add_filter('views_edit-post', 'add_custom_post_types');
    
    function add_custom_post_types($views) {
    	$views['assigned'] = '<a href="?post_status=assigned&post_type=post">test</a>';
    	return $views;
    }

    Mind you, this is nowhere near complete. You’ll need to add some more code to have it show how many posts there are of that post type, to show as selected, etc. But ‘views_edit-post’ should be the filter you need to take advantage of.

    If you need anymore help with the code, just post back here.

    If I were to hack hack hack this plugin to make it work, I would probably start with modify the following two lines:

    1. On this line, I would switch ‘DESC’ to ‘ASC’
    2. On this line, I would switch ‘prependTo’ to ‘appendTo’.

    Mind you, these are all hacks hacks hacks, and I wouldn’t condone implementing this until the core code does (if you did, you wouldn’t be able to update!). And I haven’t tested this out, so it could cause more problems than it solves.

    Daniel might have a better suggestion with a filter or action you could take advantage of that would make this less janky.

    Yea, there’s an issue with changing this, and I’ll point you to the original reason for why this filter was created. Here’s the original issue a user was encountering. Given that you use the Editorial Calendar you might no end up running into this issue very often, in order to see this problem in action do the following:
    1) Make a post on todays date from Editorial Calendar
    2) Give it a time before the current time
    3) Edit that post
    4) Publish it

    You might notice that when you publish it, the “published time” doesn’t update to the current time. That’s the problem that EditFlow tries to navigate around with this filter. Nonetheless, I’ll continue to look into this to see if there’s anything that can be done.

    Okay, took me a little bit to track this one down, but I think I figured out the problem. This filter is resetting the post_date_gmt which the Editorial Calendar relies on. I’ll take a look at how this could be fixed after I get back from class.

    Peace,
    CJ

    If you made “Syndicated” a custom post status, I believe then that yes, it would be the case that you could have posts continue to show up on the site. Just make sure to alter your loops to include it.

    This is the line you probably want to base the changes to your loop(s) off of:

    $query = new WP_Query( array( ‘post_status’ => array( ‘pending’, ‘draft’, ‘future’ ) ) );

    Thread Starter cojennin

    (@comradefuzz)

    No worries. This is something I could definitely use so I’ll get started it on asap.

Viewing 15 replies - 166 through 180 (of 193 total)