Announcement

Collapse
No announcement yet.

Secuity Patch causes display errors on sharing media links

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Wayne Luke
    replied
    That determination is out of my control.

    Leave a comment:


  • BulliM
    replied
    Just one thing: Nginx is running on more than 20% of all hardware. Maybe you think about testing your software on Nginx in future. It's my wish for christmas. Was a horrible day.

    Leave a comment:


  • BulliM
    replied
    Okay. Thank you again and especially to the gal/guy who solved that. Now I can relax and prepare me for Christmas.

    Leave a comment:


  • Wayne Luke
    replied
    The issue is fixed in 5.4.0 with the same JIRA ID as the patch file that I gave you.

    Leave a comment:


  • BulliM
    replied
    Okay. So do I have to worry about any longer? Have this on your radar?

    Leave a comment:


  • Wayne Luke
    replied
    Thanks for the feedback. Seems to be a separate bug that was exposed on your server due to the stricter handling in the patch. A support staff member also experienced the bug using an alpha build and a file that doesn't exist in 5.3.4.

    Leave a comment:


  • BulliM
    replied
    Seems to work. I'll try now on real server.
    EDIT: Works fine! Makes my day! Big hug! Thank you and Merry Christmas!
    Last edited by BulliM; Thu 21 Dec '17, 9:18am.

    Leave a comment:


  • Wayne Luke
    replied
    Try this patch.
    Attached Files

    Leave a comment:


  • BulliM
    replied
    Originally posted by Wayne Luke View Post

    We expect people using NGINX to know how to configure their servers properly. It is not a beginner's tool.
    My Nginx server is configured accurately.

    What you tell me, is not true. The patch includes "core/vb/library/template.php". You've changed something, that's responsible for my error.

    I now need access to an original vB 5.3.4. without patch for a rollback. Can I please have access to?

    Leave a comment:


  • Wayne Luke
    replied
    Originally posted by BulliM View Post

    What you want to tell me? That the error doesn't have to do with the security patch?

    Why css files loaded and delivered as html files? Look at my screenshots! I think, it causes because nginx configuration is different to apache configuration. What server vBulletin use?
    We use Apache. We don't actually provide explicit technical support NGINX or test under NGINX. We expect people using NGINX to know how to configure their servers properly. It is not a beginner's tool.

    Still the patch covers two issues... The first is an unserialize issue and.the second only occurs on Windows Servers. If you're using Windows, you shouldn't be using NGINX. Neither issue should affect the display of CSS. Nothing was changed in the templates. Nothing was changed on how CSS is delivered by the software. Under any server.

    If /core/css.php exists on your server, then you need to investigate your server configuration to understand why NGINX can't see the file and its query string and is returning a 404 error. That isn't caused by the software. If the file doesn't exist, then all CSS would be missing.
    Last edited by Wayne Luke; Thu 21 Dec '17, 8:11am.

    Leave a comment:


  • BulliM
    replied
    I now run a full upgrade from 5.3.4 to 5.3.4 Patch Level 1 on my test server. Problem is NOT solved, as expected.

    Leave a comment:


  • BulliM
    replied
    Originally posted by Wayne Luke View Post
    Your issue is completely unrelated to the patch. The patch did not cause it. The patch has absolutely nothing to do with the style of your site or loading CSS on the site.
    What you want to tell me? That the error doesn't have to do with the security patch?

    Why css files loaded and delivered as html files? Look at my screenshots! I think, it causes because nginx configuration is different to apache configuration. What server vBulletin use?

    Leave a comment:


  • Wayne Luke
    replied
    Your issue is completely unrelated to the patch. The patch did not cause it. The patch has absolutely nothing to do with the style of your site or loading CSS on the site.

    When you downloaded vBulletin, it included an upload/core/install directory. You will need to upload this directory and run upgrade.php.

    Leave a comment:


  • BulliM
    replied
    There is no upgrade.php - not even an install directory. I just overwrite with the patch files. I've already rebuilded styles in admincp with general update tools. Doesn't fix the problem, that css files delivered as html files. It is a rendering problem.
    Last edited by BulliM; Thu 21 Dec '17, 7:09am.

    Leave a comment:


  • Wayne Luke
    replied
    Please run the upgrade.php file to rebuild your styles.

    Leave a comment:

widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
Working...
X