neocreo

Well, smack my bottom and call me Zoot.
Feel very silly now. I had checked the location of the original files – missing the newly created folder in the root of the uploads folder. Of course I had to move all the uploaded documents via FTP to this new location.

I hope someone else can learn from my foolishness.

OK, if anyone is interested, I solved it the following way – and hopefully the author sees this – might add this to the next version of the plugin.

I only needed this run when first uploading a document, so I hacked the following file: wp-content/plugins/wp-document-revisions/js/wp-document-revisions.js
I ran the code through jspretty to find the correct place.
find the prototype
WPDocumentRevisions.prototype.postDocumentUpload = function (file, attachmentID)
At the end of the function I added the following jQuery

var filename = file.split(".")[0];
            if (this.window.jQuery('#title').val() == '') {
            	 this.window.jQuery('#title').focus().val(filename);
            };

What is does is simply checking whether the document title is empty, if so it will set the focus on the field and fill it with the file-name with the file ending removed.

I think it could be useful for new users, especially since the filename is not visible anywhere after upload.

Thanks Andrew,
Guess I will give it a whirl with building a wordpress plugin.
However, an idea for a future version: Would it be possible for tinymce advanced to simply look inside the MCE directory and simply add on the plugins with the same names as the directory?

That would minimize the need for editing and users can simply drop plugin-folders. Keeping the extra folders as a list in the settings for the plugin could even keep them from being deleted when upgrading. Or even simpler: have a separate folder for them outside of the core, for instance under the theme directory. If the folder is there, then load the editor_plugin.js files inside the directories.

Just an idea. I love your plugin. It is very easy and straight forward to use.

I have a similar question – I am trying to add the imgmap plugin (for tinymce). Seriously though Andrew, you are not suggesting having to install a separate wordpress plugin to add that on?

I think Chris, like myself just want to add more plugins than what is included with the install.

I reckon the added text need to be done in the tadv_admin.php after uploading the plugin folder?

All that really is the question is exactly what one need to add and to what function.

Of course, this would mean that an update of the plugin would wipe away any changes, but that is not really a big issue.

Hi Hal,
Actually I am looking at this right now. The data is in the array you get from the openweather API would be to build something like this:
$rtn .= "<img src=\"https://openweathermap.org/img/w/{$today->weather[0]->icon}.png\" >";
It is a dirty fix, but could just as easily be set using the ID-codes from open weather and using your own icon library, which would allow for even greater detail and other sizes. I’d be happy to help if you want?

Auto sort is on everywhere. Sorted in the correct place (main page for my archive), Still no luck with this. Cannot get it to work with have_posts() and the_post().

However, managed to get sorting in the front-end working somewhat using WP_Query() and specifying

'orderby'                   => 'menu_order',
'order' => 'ASC',
'force_no_custom_order'     => TRUE

as arguments for the WP_Query(). Is a wee bit annoying as now the pagination won’t work as expected and it also gives me trouble with filtering the content according to my custom taxanomy.

I just wonder what it might be that makes it completely ignore the custom sort order when just grabbing the posts through if (have_posts()) : while (have_posts()) : the_post();?

The thing is that I bought this one because the free version actually worked on my pages with no code changes.

Have sent my request onwards on the nsp-code.com page.

Thanks @imath
I suspected as much, and indeed, there seem to be a conflict in there. I have tested on both Ubuntu and OSX, but of course, silly me, I did not test the error in all browsers. Firefox for normal users seem to work just fine, so the error only affects webkit browsers. Clearly a clash of javascript that should not even be loaded on that page.

Thanks for taking the time and spotting my noobie mistake!