Get started with PHP-Fusion

Start a New Thread

Users Participated

  • Sveinungs
    Post made: 3
  • Drbo
    Post made: 5

  1. PHP-Fusion Support Forums
  2. PHP-Fusion 6 Support
  3. Bugs and Errors

Little bug in print.php with Character Encoding

Forum Locked - v6 no longer supported

7 Replies 2,334 Views Last Updated on 8 years ago

Drbo


Senior Member

#1

Posted 8 years ago

I did show one of the news in printer-friendly format, check validation on validator.w3.org and this errors apears:

1)
No Character Encoding Found!

2)
No DOCTYPE found! Attempting validation with HTML 4.01 Transitional.

What is missing in print.php script?

Posts: 258

Joined: 30/09/2006

Drbo


Senior Member

#2

Posted 8 years ago

Nobody? Help me, please...

Posts: 258

Joined: 30/09/2006

Sveinungs


Veteran Member

#3

Posted 8 years ago

Try this, changes marked in bold.

Code Gist: Download source  
echo "[b]<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\">[/b]
<html>
<head>
<title>".$settings['sitename']."</title>
[b]<meta http-equiv='Content-Type' content='text/html; charset=".$locale['charset']."'>[/b]
<style type=\"text/css\">
body { font-family:Verdana,Tahoma,Arial,Sans-Serif;font-size:14px; }
hr { height:1px;color:#ccc; }
.small { font-family:Verdana,Tahoma,Arial,Sans-Serif;font-size:12px; }
.small2 { font-family:Verdana,Tahoma,Arial,Sans-Serif;font-size:12px;color:#666; }
</style>
</head>
<body>\n";


This defines the doc-type, and what carset to be used, and your page should validate.

Posts: 937

Joined: 05/04/2006

Drbo


Senior Member

#4

Posted 8 years ago

Great, it works! The page is valid... Thank you very much... I have two troubles with Expanded Calendar... Do you use this infusion?

Posts: 258

Joined: 30/09/2006

Sveinungs


Veteran Member

#5

Posted 8 years ago

Nope Smile

Posts: 937

Joined: 05/04/2006

Drbo


Senior Member

#6

Posted 8 years ago

Itīs a pity... This is great infusion with two little bugs with validation again...

Posts: 258

Joined: 30/09/2006

Sveinungs


Veteran Member

#7

Posted 8 years ago

Maybe do this the hard way then?

Use W3C validation page,
have them point out the errors,
view source code from your page,
then try to find those errors in your infusion source code,
correct it - and presto!

Might be a learningful experience, and the error might be easily corrected. Wink

Posts: 937

Joined: 05/04/2006

Drbo


Senior Member

#8

Posted 8 years ago

I did it by this way, but I have no experience with the php coding... Can I describe this problem to you?

Posts: 258

Joined: 30/09/2006

Jump to Forum:
10 users are online
0 member and 10 guests