1 hullodare Jul 05, 2004 03:13
3 hullodare Jul 05, 2004 17:49
Thanks for the response. Where exactly do I "find it"? If I hit view > source in IE6 I can see it. I'm using Dreamweaver as an editor. I post through IE6. Can you point to the right file so I can fix this thing? Thank you.
4 demonraiser986 Jul 05, 2004 18:35
View Code in Dreamweaver will allow you to get to that line.
I would recommend using UltraEdit www.ultraedit.com for any code fixing/tweaking.
the file should be index.php
5 hullodare Jul 06, 2004 06:20
:( I looked at the index.php files. There are more than one. It doesn't have 167 lines in it. Please tell me how to edit this code in Dreamweaver or any text editor you want (I do have ultraedit BTW). I have a whole slew of files on the remote server and I have no clue where to look for the code I am trying to fix. I looked at index.php and saw nothing resembling the code I get when I hit view > source in IE6. I'm pretty good with html and css. I'm new to php. I just can't find the file or code that needs fixing. Please help me and spell out the instructions clearly. Thank you.
6 hullodare Jul 06, 2004 06:30
I clearly see the code in Ultraedit on line 167 and it's easily fixable with a quick edit. But!!! I don't know where to edit which file on the server. Plus: Why can't I view the text I post? I can see it in IE6 with the view > source. But I can't find my posted text on my server. Help me please. :oops:
7 isaac Jul 06, 2004 07:55
This is the offending link:
167: <a href="/blogs/index.php?page=1&disp=posts&paged=2&page=1&disp=posts&paged=1"><< Previous Page</a> :: ...
The error is most likely happening on line 118-124 of .../blogs/skins/custom/_main.php.
<p class="center"><strong>
<?php posts_nav_link(); ?>
<?php
// previous_post( '<p class="center">%</p>' );
// next_post( '<p class="center">%</p>' );
?>
</strong></p>
[url=http://isaacschlueter.com/all?skin=custom]I can't repro it.[/url] If you've done anything to change any of the URL-generating functions, then that was probably the mistake. If not, wait for the next release, as it's most likely corrected.
8 graham Jul 06, 2004 08:14
And the text of your posts is stored in the database, you'll need to log into phpmyadmin or something like that to see the text you post.
9 hullodare Jul 06, 2004 17:32
isaac wrote:
This is the offending link:
167: <a href="/blogs/index.php?page=1&disp=posts&paged=2&page=1&disp=posts&paged=1"><< Previous Page</a> :: ...
The error is most likely happening on line 118-124 of .../blogs/skins/custom/_main.php.
<p class="center"><strong> <?php posts_nav_link(); ?> <?php // previous_post( '<p class="center">%</p>' ); // next_post( '<p class="center">%</p>' ); ?> </strong></p>
[url=http://isaacschlueter.com/all?skin=custom]I can't repro it.[/url] If you've done anything to change any of the URL-generating functions, then that was probably the mistake. If not, wait for the next release, as it's most likely corrected.
=> I did nothing to change any of the URL-generating functions. So...no "mistake" on my part. Wait for the next release? Why can't I correct the situation now?
10 isaac Jul 06, 2004 17:52
Looks like I spoke too late. Madrid has been released, but there is a [url=http://b2evolution.net/dev/todo/2004/07/05/mysql_error_table_evo_xxx_does_not_exist]bug in the upgrade procedure[/url]. You can either use the workaround provided, or wait for 0.9.0.10. Either way, it'll correct the invalid XHTML problem.
11 hullodare Jul 07, 2004 06:00
I'll wait for 0.9.0.10. Thanks for the response.
12 hullodare Jul 07, 2004 17:29
I installed Madrid and the invalid code problem is solved. I checked everything out in w3c validating service and it's all good. Thanks for the great advice as usual. BTW: The new default custom page is really well done. Beautiful design.
the ampresand error on line 167 will be a common thorn in anyone obsessed with validation but luckally very easy to fix.
XML will not render '&' because it expects a charactor entity, therefore XHTML wont validate it. Find and replace all offending '&' with '&'
fixing that one instance (so far) of '&' will clear ALL of those validation errors listed.