Results 1 to 6 of 6
  1. #1
    Join Date
    Jul 2013
    Location
    Budapest, Hungary
    Posts
    22
    Points
    1,556
    Level
    16

    Missing CSS on Site Disabled Page

    Hi,

    I have some problems with the default Site Disabled page. The iworx-error.css is missing, the apache return 404.

    The HTML is:
    HTML Code:
    <!DOCTYPE html>
    <html xmlns="http://www.w3.org/1999/xhtml">
      <head>
        <title>Site Disabled</title>
        <link rel="stylesheet" media="screen" href="../iwx-error.css"/>
      <body>
        <div id="wrapper">
          <div id="content">
            <div id="content-inside">
              <div id="bigx">
              </div><!--/bigx-->
              <h1>This Site Has Been Disabled</h1>
              <h2>Contact your service provider for more information.</h2>
            </div><!--/content-inside-->
          </div><!--/content-->
        </div><!--/wrapper-->
      </body>
    </html>
    Last edited by vrnagy; 12-03-2013 at 07:15 AM.

  2. The Following User Says Thank You to vrnagy For This Useful Post:


  3. #2
    Join Date
    Apr 2012
    Posts
    2,179
    Points
    24,164
    Level
    67
    Hi Vrnagy

    I hope your well

    I have had a quick look on our system, and the missing css file should be shown in this area, /usr/local/interworx/var/errors

    I hope it helps

    Many thanks

    John

  4. #3
    Join Date
    Jul 2013
    Location
    Budapest, Hungary
    Posts
    22
    Points
    1,556
    Level
    16
    Hi Johsn,

    Thanks for the reply. The file exists in /usr/local/interworx/var/errors, but not exists in apache environment, maybe caused by some missing apache configuration?
    I did not changed any apache related configuration on the server.


    After some research, i found the root of the problem.
    In the apache config the disabled site's document root is /home/interworx/var/errors/disabled but in that directory, there is no iwx-error.css and apache can't handle the ../iwx-error.css link to the main directory.
    Maybe a quick fix is a symbolic link.

  5. The Following 2 Users Say Thank You to vrnagy For This Useful Post:


  6. #4
    Join Date
    Apr 2012
    Posts
    2,179
    Points
    24,164
    Level
    67
    Hi Robert

    Good point, and I just tested in our server and it does not appear to use the iw error.css file either.

    I'm thinking ahead a little here, so sorry if I'm wrong, but if symlinked, and the future updates from IW are installed, but let's say they move the CSS file, would that not cause a reverse failure if using symlinked.

    Perhaps a better idea would be to move the CSS folder into the disabled folder, and tweak the php on the disabled file, which should work I think, and I'll email Mr T about this, so it can be corrected on future updates.

    I hope this makes sense and I'm sorry if I'm wrong, I was just thinking ahead and how it might be affected, as symlinked files or folders could easily be forgotten they exist.

    Many thanks

    John

  7. #5
    Join Date
    Sep 2012
    Posts
    67
    Points
    4,333
    Level
    27
    This might file as a bug.

    I know we ended up just combining all of the CSS (and base encoded images) into the HTML file for the SKEL-placeholder-new-site-file.

    This simplified the amount of files for a new domain and made stuff more clean.

    D2's got the fastest solution with the least headache for now.

    If you'd like me to combine the error HTML + Images + CSS in to a single file for you as a temporary fix, I'd be happy to.

    But I'll look into this today.

  8. The Following User Says Thank You to IWorx-Trevor For This Useful Post:


  9. #6
    Join Date
    Oct 2009
    Location
    Netherlands, Tilburg
    Posts
    8
    Points
    3,052
    Level
    23
    This problem still exist.
    ---
    Mart Dirks -- Gewoon IT -- The Netherlands

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •