Forum Replies Created
-
Posts
-
Think I’ve sorted it myself, but with the rather ugly
.av-main-nav ul {
top: 60%;
}Now I’m just looking to try and get pages to load with the shrinking header shrunk when the page loads.
Resolved this myself with a quick bit of jQuery in the footer. Probably not the most elegant solution, but it seems to work.
function avia_custom_resizer(){ ?> <script type="text/javascript"> jQuery(window).scroll(function(){ var view_height = jQuery(window).height() - (jQuery("#wpadminbar").height() + jQuery("#header_meta").height() + jQuery("#header_main").height()); jQuery("#av_section_2 .container").height(view_height); }); </script> <?php } add_action('wp_footer', 'avia_custom_resizer');in functions.php, seems to do the trick.
The temporary file, which is the zip file being downloaded, is created in C:\Windows\Temp; the upload_tmp_dir directive location. However, it is the extraction of the zip file which is failing, when it attempts to create the output directories in the WordPress upgrade folder. This is where the limitation comes in to play. The article relates to URL length so isn’t relevent, this has more detail on the NTFS limits, including that Windows can support longer paths, but only if you call Unicode versions of the functions with a modified version of the path!! https://msdn.microsoft.com/en-gb/library/windows/desktop/aa365247%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396#maxpath
The limitation is not the URL, but in the NTFS filesystem. The maximum file path in Windows current versions is 260 characters, including the drive letter assignment and trailing NUL character. In the example I gave, this download file path in the C:\Windows\Temp directory is 247 characters. When the zip file is being extracted however, it tries to create a folder in C:\IMCWebsiteDev\wwwroot\wp-content\upgrade named with the long file name. In total this comes to 272 characters, so directory creation fails and we get the error message.
The good news is that I’ve submitted a simple patch to WordPress Core, and it looks as it will be out in the build fairly soon.
If anyone wants to fix this issue on their site, the required edit is in wp-admin/includes/file.php where you edit line 457 (v4.2.2, other versions may vary) The edit required is to change
$tmpfname = wp_tempnam( $url );
to
$tmpfname = wp_tempnam( parse_url( $url, PHP_URL_PATH ) );
to strip off the query string from the resulting filename. THIS IS AT YOUR OWN RISK!!! but it has worked on my installs.–Richard
I’ve had the same issue the last few updates, but wasn’t sure if it was WordPress or Enfold related. However, recently I’ve done a major batch of updates and Enfold is the only update I’ve experienced this issue with, on both live site and my local laptop copy I use for plugin development.
Doing a process monitor exercise, I’ve found that during the update process, the file created in the temporary upload folder, in my case C:\Windows\Temp is named:
enfold.zipAWSAccessKeyId*******************Expires1437422162Signature*****************-***********-3Dresponse-content-dispositionattachment-3B-filename-3Dthemeforest-4519990-enfold-responsive-multipurpose-theme-wordpress_theme.tmp
(AccessKeyId and Signature obscured, but at correct length)
this then breaks windows file system path length limits when an attempt is made to move it into the PHP working path.The URL requested for the update was:
https://s3.amazonaws.com/marketplace-downloads.envato.com/files/140862862/enfold.zip?AWSAccessKeyId=*******************&Expires=1437422162&Signature=*****************-***********%3D&response-content-disposition=attachment%3B+filename%3Dthemeforest-4519990-enfold-responsive-multipurpose-theme-wordpress_theme.zipIt’s clear that this is the updater attempting to use the entire URL passed to Envatos AWS service, including the query string, as the filename, instead of just enfold.zip. This almost certainly appears to be an updater issue within Enfold, not a configuration issue, but will only show up on Windows hosts where path length comes in to play.
* Edit *
It may be possible to quick fix this by shortening the zip file lodged with Envato if possible? Change it from themeforest-4519990-enfold-responsive-multipurpose-theme-wordpress_theme.zip to something shorter perhaps? That may fix it for some people depending on WordPress installation paths.
I have also raised this as a bug with the WordPress Core dev team, with the suggestion that the download_url() function in WordPress removes query strings from URLs before creating temporary files based on them.Many thanks,
RichardThanks, step 2 sorted it. Deactivating plugins didn’t work but reinstalling from a download of 3.0.4 did the trick.
I’ve re-enabled all plugins, and re-enabled Avia in posts, and all seems well.–Richard
