The following warnings occurred:
Warning [2] Undefined array key "profilelink_plain" - Line: 5 - File: inc/functions_post.php(951) : eval()'d code PHP 8.1.26 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/inc/functions_post.php(951) : eval()'d code 5 errorHandler->error_callback
/inc/functions_post.php 951 eval
/showthread.php 1121 build_postbit
Warning [2] Undefined variable $useravatar - Line: 5 - File: inc/functions_post.php(951) : eval()'d code PHP 8.1.26 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/inc/functions_post.php(951) : eval()'d code 5 errorHandler->error_callback
/inc/functions_post.php 951 eval
/showthread.php 1121 build_postbit
Warning [2] Trying to access array offset on value of type null - Line: 5 - File: inc/functions_post.php(951) : eval()'d code PHP 8.1.26 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/inc/functions_post.php(951) : eval()'d code 5 errorHandler->error_callback
/inc/functions_post.php 951 eval
/showthread.php 1121 build_postbit




Do you hard-code or use a WYSIWYG?

4 Replies, 15084 Views

I prefer to code from scratch most of the time, because the code is more streamlined that way than it is when making a site with a WYSIWYG (or "design view"), which usually bloats the code badly and makes for longer loading times.
i didnt heard about that..looks to be different..
fashion blog
I like WYSIWYG. Its easier to edit the posts that way. I am not aware that is slows the loading down though
I also like to use WYSIWQYG.  It is faster most of the time, although I often have to go back and make changes.  Starting from scratch can be cumbersome, but it can also be a good friend when you are starting on something completely different.
I use both but most WYSIWQYG Big Grin
Ihost4you.com



Users browsing this thread: 1 Guest(s)