close ad
Install the LAtest Updates to Work with CC 2017 and CC 2018
open ad
View Menu

Technical Support Forums

Free, outstanding support from WebAssist and your colleagues

My WA Framework Feedback and Suggestion whistlist

Thread began 8/11/2010 3:49 pm by victor278184 | Last modified 8/13/2010 5:58 pm by victor278184 | 1552 views | 12 replies

Ray BorduinWebAssist

1) I'm not sure if there is any benefit to using a plugin if it is pure php code. Why not just use require_once()? The whole advantage of plugins over a standard require_once() is that it will deconstruct a full page and break it into it's component pieces... updating necessary links and other references and then place it into the correct corresponding location on your page. If it is pure php it wouldn't know whether that code belongs in the head or the body, so you would have to place it manually to the correct location.

In your case you could still use it, but you would want to delete the header and title references from the page that are automatically placed, since you aren't using them.

It probably is a bug though. Technically they should all three be blank and you should have to refer to the ->Contents of the plugin to return a result since there is no head, body, or title defined. I'll log a bug to get this fixed.

2) Remove the meta information from plugins where you don't want it added... you could also remove the head reference and instead add the css and scripts individually as well as just the meta from the plugin that you want to actually use. In order to keep it simple we include the entire head, which will include meta information if the plugin page has it. If multiple plugins have meta information, there is no way to prioritize which should or shouldn't be used, so it would have to be a human decision at some point. It seems the easiest route would be to simply remove the meta tags from plugin pages where you don't want or need them.

I will log a feature request to add a binding for "Header without meta" and to ask if you want to include the meta information when applying each plugin. This would allow you to make that decision during application more easily instead of having to remove the meta tags from the plugin pages beforehand.

Build websites with a little help from your friends

Your friends over here at WebAssist! These Dreamweaver extensions will assist you in building unlimited, custom websites.

Build websites from already-built web applications

These out-of-the-box solutions provide you proven, tested applications that can be up and running now.  Build a store, a gallery, or a web-based email solution.

Want your website pre-built and hosted?

Close Windowclose

Rate your experience or provide feedback on this page

Account or customer service questions?
Please user our contact form.

Need technical support?
Please visit support to ask a question

Content

rating

Layout

rating

Ease of use

rating

security code refresh image

We do not respond to comments submitted from this page directly, but we do read and analyze any feedback and will use it to help make your experience better in the future.

Close Windowclose

We were unable to retrieve the attached file

Close Windowclose

Attach and remove files

add attachmentAdd attachment
Close Windowclose

Enter the URL you would like to link to in your post

Close Windowclose

This is how you use right click RTF editing

Enable right click RTF editing option allows you to add html markup into your tutorial such as images, bulleted lists, files and more...

-- click to close --

Uploading file...