Ashley Sheinwald
Forum Replies Created
-
This has been updated in the latest version of the plugin. So all good now 🙂
Forum: Plugins
In reply to: [Contact Form 7] 403 error on page load with hidden formSome additional data – in case it helps find the issue.
Remote address and Request URL domain obscuredRemote Address:xxx.x.x.x:80
Request URL:http://domain/?_wpcf7_is_ajax_call=1&_wpcf7=108&_wpcf7_request_ver=1414058539136
Request Method:GET
Status Code:403 Forbidden
Request Headersview source
Accept:application/json, text/javascript, */*; q=0.01
Accept-Encoding:gzip,deflate,sdch
Accept-Language:en-US,en;q=0.8
Cache-Control:no-cache
Connection:keep-alive
Cookie:PHPSESSID=c185ff8c19de02e39d52cf4ccae9d81c; wp-settings-3=libraryContent%3Dbrowse%26editor%3Dhtml%26hidetb%3D1%26advImgDetails%3Dshow%26wplink%3D0%26ed_size%3D360%26imgsize%3Dthumbnail%26align%3Dleft; wp-settings-time-3=1413909034; bb2_screener_=1414058517+127.0.0.1; wordpress_test_cookie=WP+Cookie+check; mp_774f6b0c47772e7c4d159eb5694455ad_mixpanel=%7B%22distinct_id%22%3A%20904114099%2C%22%24initial_referrer%22%3A%20%22http%3A%2F%2Fdomainname%2F%22%2C%22%24initial_referring_domain%22%3A%20%22domainname%22%7D; _ga=GA1.2.499312045.1414055226; _gat=1
DNT:1
Host:domainname
Pragma:no-cache
Referer:http://domainname/
User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.104 Safari/537.36
X-Requested-With:XMLHttpRequest
Query String Parametersview sourceview URL encoded
_wpcf7_is_ajax_call:1
_wpcf7:108
_wpcf7_request_ver:1414058539136
Response Headersview source
Connection:Keep-Alive
Content-Encoding:gzip
Content-Length:246
Content-Type:text/html; charset=iso-8859-1
Date:Thu, 23 Oct 2014 10:02:19 GMT
Keep-Alive:timeout=15, max=97
Server:Apache/2.0.63 (Unix) PHP/5.3.2 DAV/2
Vary:Accept-EncodingForum: Plugins
In reply to: [Post Thumbnail Editor] Open Editor in a new windowOf course, I’m not one to pressure a developer 🙂
Anyway, the workflow I was referring to was retrospectively editing images and thumbnails from the media library itself not while editing a post. Sometimes the user workflow is to upload images to library to use later etc. and it was via here I was referencing the differences in link functionality and screen views.
Seeing as how responsive and helpful @sewpafly has been I’m sure this is just around the corner 😉
Great work and thanks for quick usable fix!
Forum: Plugins
In reply to: [Post Thumbnail Editor] Open Editor in a new windowFirstly, it’s a great plugin, very useful and functional for users on the screens where it displays – functionality wise (concept) this should be in core.
Per master zip
From link on “Attachment details” [Page] it opens in the main frame so still have access to main menu, but it is a pity that the “Post thumbnail editor” link does not open a pop over the way the “Post thumbnail editor” [Button] does – from the “Edit Media” [Page]Also, for improved usability and consistency it is a shame that the “Post thumbnail editor” [Button] is missing from the “Attachment details” [Page] -> after clicking the edit button.
For end users, editors etc. it is a bit of a mind-field to find out how and where this functionality is, if not stumbling across it. Otherwise, it is functional and very handy!
So thanks 🙂Forum: Plugins
In reply to: [Post Thumbnail Editor] Open Editor in a new windowOK 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:84Browsers tested
Apple
Chrome: Version 37.0.2062.124
Firefox: 28.0
Safari: 7.1Note:
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
http://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
Forum: Plugins
In reply to: [Post Thumbnail Editor] Open Editor in a new windowOK,
Trying to help out here and yes there are a few touchpoints for the plugin to display properly.
Attachment Details -> Edit Image button
– No OptionsAttachment 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
http://address/wp-admin/admin-ajax.php?action=pte_ajax&pte-action=iframe&pte-id=875Console states
GET http://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 http://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:84HTH
Forum: Plugins
In reply to: [Post Thumbnail Editor] Open Editor in a new windowTesting 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!
Forum: Plugins
In reply to: [Post Thumbnail Editor] Hook into crop for black and white manipulationSolved – added additional filter to hook wp_update_attachment_metadata
add_filter(‘wp_update_attachment_metadata’,’function_name_for_grayscaling’);
Will do.
Will have to remove the login details Wednesday night as it is a client site and goes live Thursday.
Filling in report now.