Open Editor in a new window

Yes, you should be able to just right-click on the link and choose to open in a new window/tab as you want.

Yes absolutely that can be done but it’s incorporated in a company theme for marketing managers in 27 countries who are not as technically inclined.

It would be easier for them if the editor opened in a new window so they don’t lose their admin screen.

Sorry, I’m not following very well. When you say screen do you mean a new browser tab/window, or do you mean a new widget on top of the admin interface?

Currently PTE follows the wordpress interface pretty closely in that if you just follow the clicks, it will (well, it should) only open in widgets in the current browser tab or window *over* the wordpress admin. This is from functionality included in wordpress, closing the box by clicking away or clicking the close button should return you to the correct wordpress page.

If you want to open the PTE interface in a standalone fashion, currently the only way is via the right-click method, which shouldn’t be too hard to explain, as the PTE crop interface is WAY more complicated than this ??

I’m finding that the OP is correct and the plugin opens over the top of every administrative function and has no close button! Any clues?

Corinne

@corinnepritchard – can you upload a screenshot? There are several entry points to the PTE interface, which one do you use?

Testing here with WP 4.0 if from the Media Library I select an image then via the text links in the grey column on the right (editor column) – View attachment page | Edit more details | Delete Permanently Post Thumbnail Editor

If I select “Post Thumbnail Editor” it opens without a way to return to the media library, pr or post editing and there is no close option either!

OK,

Trying to help out here and yes there are a few touchpoints for the plugin to display properly.

Attachment Details -> Edit Image button
– No Options

Attachment Details -> Edit More details Link -> Edit Media screen
– PTE button [All good – opens as pop over]

Per original msg above:
Post Thumbnail Editor link from ‘attachment details screen’ loads IN window,
URL states
https://address/wp-admin/admin-ajax.php?action=pte_ajax&pte-action=iframe&pte-id=875

Console states
GET https://address/wp-content/plugins/post-thumbnail-editor/apps/angular/angular.min.js.map 404 (Not Found) /wp-content/plugins/post-thumbnail-editor/apps/angular/angular.min.js.map:1
GET https://address/wp-content/plugins/post-thumbnail-editor/apps/angular/angular-resource.min.js.map 404 (Not Found) /wp-content/plugins/post-thumbnail-editor/apps/angular/angular-resource.min.js.map:1
Disabling loading screen angular.min.js:84

HTH

Full screen happens to me regardless of whether I’m uploading in a post or going through the media list.

Screenshot 1: before: https://www.dropbox.com/s/1fublzlg5hum71r/Screenshot%202014-10-07%2014.51.06.png?dl=0

Screenshot 2: after:
https://www.dropbox.com/s/6u6telr5ibc1z84/Screenshot%202014-10-07%2014.51.19.png?dl=0

Same url framing as ashleysheinwald above.

Console error of ‘Disabling loading screen’ for no apparent reason.

Corinne

Here is what I see: https://imageshack.com/a/img540/9271/K6fuku.jpg

If you see something different, there is probably a conflict with another plugin. If you can determine which plugin is causing the problem (by deactivating them), I can make a fix for it. (The javascript console might have a clue as well).

Alternately, you could use the list view in the media library which works the way wordpress < 4.0 did.

I have deactivated every single plugin but this one and still get the same result.
And the point is as the original poster above – people who aren’t wordpress coders and administrators have to use it.

Corinne

@ashleysheinwald, @corinnepritchard – thanks for your help. This seems to be a sneaky bug, as I can’t duplicate it. From what I can tell (via the screenshots and the URL states) the browser is navigating directly to the pop-up page url. This means that the javascript isn’t catching the click correctly. (If you have the javascript console up when you click the link, do you see any error messages before the page navigates away? – you might have to enable the “preserve log upon navigation” option to see it)

* What web browsers are you using? (name/version/os)?

I might have a fix I can try (but since I can’t test I’ll need your help). I’ll also change the default URL to stay in the wordpress interface as the fallback url instead of the iframe one that you 2 are seeing.

Hmm… how odd! I have just tried the insert media option in a post and it’s suddenly doing what it’s supposed to there. However it still isn’t in the media grid. Going to try it on an Editor level account now.

I’m in the latest version of Chrome, on OSX.
Happy to assist if it helps get a fix on what’s happening!

There may be an issue with when admin-ajax is called in the media list in grid view? Clicking ‘thumbnails’ in list view does seem to keep it in the admin area.

Corinne

OK a bit more data – just ran another test with debug, this time in FF
log.txt showed nothing of value as the error is JS related which prevents the pop over instantiation and resolves to a window load.

Console extract of value!
Use of Mutation Events is deprecated. Use MutationObserver instead. script.js:20
SyntaxError: Using //@ to indicate sourceURL pragmas is deprecated. Use //# instead require.js:73
SyntaxError: Using //@ to indicate sourceURL pragmas is deprecated. Use //# instead require.js:47
SyntaxError: Using //@ to indicate sourceURL pragmas is deprecated. Use //# instead require.js:45
SyntaxError: Using //@ to indicate sourceURL pragmas is deprecated. Use //# instead require.js:395
SyntaxError: Using //@ to indicate sourceURL pragmas is deprecated. Use //# instead require.js:102
SyntaxError: Using //@ to indicate sourceURL pragmas is deprecated. Use //# instead require.js:277
SyntaxError: Using //@ to indicate sourceURL pragmas is deprecated. Use //# instead require.js:84
SyntaxError: Using //@ to indicate sourceURL pragmas is deprecated. Use //# instead require.js:79
SyntaxError: Using //@ to indicate sourceURL pragmas is deprecated. Use //# instead require.js:58
SyntaxError: Using //@ to indicate sourceURL pragmas is deprecated. Use //# instead require.js:130
“Disabling loading screen” angular.min.js:84

Browsers tested
Apple
Chrome: Version 37.0.2062.124
Firefox: 28.0
Safari: 7.1

Note:
Safari console additionally shows:

[Error] Error: Load timeout for modules: cs!apps/pteApp,cs!controllers/PteCtrl,cs!controllers/TableCtrl,cs!controllers/CropCtrl,cs!controllers/ViewCtrl
https://requirejs.org/docs/errors.html#timeout
aa (require.js, line 8)
v (require.js, line 12)
C (require.js, line 14)
completeLoad (require.js, line 28)
(anonymous function) (require.js, line 22)
(anonymous function) (require.js, line 8)
(anonymous function) (cs.js, line 150)
onreadystatechange (cs.js, line 63)
[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (angular.min.js.map, line 0)
[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (angular-resource.min.js.map, line 0)

Page never loads in Safari at all!

HTH

Can you try the latest @ https://github.com/sewpafly/post-thumbnail-editor/archive/master.zip

That seems to have done the trick.

Thanks!

Corinne