FrontPage protection from server abuse

[Mark Stewart]

Stefan B Rusynko,

You have not answered my question. It's not that the host has the roles set
wrong. The host is deliberately tracking my styling efforts and resetting
roles to block the text book methods I am using to style my sites using
FrontPage 2003! Actually, at times it appears to be far more delinquent than
that. Is this being done for Microsoft? Rediculous, right?. The host says I
have to pay more if I want to do more. But hey! We are following the book!
The host is deliberately tracking and attacking my code one plus years! Is
there some code of ethics attached to this? Why did Microsoft design
software and direct it's servers to attack user code? Where do we turn for
support about this rather unpleasant FrontPage problem?

My question is very simple. Is there a way to get past predatory host
obstruction of basic FrontPage functionality?

===PARTICULARS===

I am [strategically] applying style to Windows SharePoint Services sites,
using many methods detailed in Microsoft Press publications for WSS. My
sites are on Front Pages Web Hosting, a Microsoft recommended FrontPage
host. Everytime I get something working, my host deliberately disables my
code and the method I used to apply style to the site. The code works for a
while and then, suddenly I cannot reapply style to my suddenly messed site
using the same method. Kirk Duanes (as far as I know the only technician at
FWHN) tells me, "I am going to have to do this beacuse you are on a virtual
shared server and you are going to wreck everbody else's site if something
doesn't happen." He refuses to elaborate, telling me, "You are too stupid to
understand."

Design schedule is directly related to site stability. Daytimes are hell:
when I set proper class and ID attributes something or someone is deleting
or moving my attributes to other tables and objects on the page. and
otherwise making a mess of my pages. Some days. while I am working every
5-15 minutes my code is attacked. The attack frequently seriously disables
my site so I have to call support where I am always routed to Kirk. (I
thought FWHN was a big company.) When i create style sheets and apply the
changes after hours, the attack takes far longer to appear: it takes one day
to several months for the code attack to occur. Then the method I used is
blocked and my site is messed up. I keep asking myself, why would a
Microsoft recommended host be doing this? Or is this Kirk individual
attacking us on his own and somehow writing server rules for just our site?
I have advised Kirk that certain aspects of our site are a life and death
matter, so I find it difficult to believe anyone would obstruct us so
callously.

I am a web designer, not a secretary. I am not-for-profit but I do
legitimate work - e.g., a project with the national government to reduce
avalanche deaths. Last week three more deaths, one European and two Candian
fatalities. I consider, should we take action in court, make an
international noise? That might be easy, but we don't want to damage
Microsoft, do we? We are using FWHN for cost reasons. We keep hoping for
improvement in service, and looking for ways to bypass the
[[[UNADVERTISED]]] style for cost excuses that Kirk imposes on us. "What can
we do, Kirk?" "Oh, I'm not sure. We'll have to wait and see." The very same
question and answer every month for a year.

Is FWHN moving on to Expressions? So I check out Expressions Web Designer on
http://mountainclubs.ca and note that after one or two site entries my login
is permanently fried, even after I uninstall Expressions and return to
FWHN's butchered FrontPage. Another chat with Kirk, of course. I want to
challenge Kirk about the Expressions platform and the apparentlly backwards
direction being taken by the anti-style FWHN he has served up for us. But
then I am again wondering why I am always talking to Kirk and realizing it
could be weeks or months befor it is safe to touch our site at night. Oops!
By then my login will be lost; I'll email support - and we'll end up in
another chat with ...Kirk.

My question is very simple. Is there a way to get past predatory host
obstruction of basic FrontPage functionality? Perhaps some script that
conceals frontpage aspects of code from the server. A way to develop the
site but trick the server into not noticing any change to site structure?
The world I service deserves to benefit from and enjoy site design the way
FrontPage is designed to deliver it. Lawyer, heart-to-heart, script
intervention - what do we do? Are there affordable servers out there who
actually let you design without any interference?

Regs, mark.stewart

cc Executive Director, The Federation of Mountain Clubs of British Columbia

If you are being blocked from using / changing themes on a WSS server
- the host does not have the roles set correctly
(or you do not have Web Designer or Administrator rights)
-
http://www.microsoft.com/resources/documentation/wss/2/all/adminguide/en-us/stsf01.mspx?mfr=true
Also see
http://www.sharepointcustomization.com/resources/tipstricks/wss_cssguide.htm
--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
_____________________________________________


| http://sbrenjoy.bizland.com/frontpage/themes/newthemes.html#Granular
|
| The link above describes how vbs can manipulate styles, and makes me
wonder
| if my virtual SharePoint host is manipulating my design by eliminating
all
| FrontPage style capability. My host is Front Pages Web Hosting, and I
thought
| by its name and Microsoft lables everywhere that it would support the
| FrontPage product on its SharePoint servers.
|
| One of my sites is http://www.mountainclubs.bc.ca and services about
5,000
| registered users. Due to ongoing problems fitting design to
organizational
| requests, the site is none too popular. The situation is that Front
Pages Web
| Hosting has questioned me for months about using FrontPage Theme
| customization. Beginning last week, any attempt I make to customize a
theme
| is completely ignored. In fact, not only are theme changes undone, but
all
| new related web part page content is deleted along with the theme
change!
|
| FWHN refers to my theme work as their "project". Here's how my theme
| "project" had to progress.
| 1. Initial success was had simply creating/editing a user defined style
with
| www.mountainclubs.bc.ca open in FrontPage. This is when techniical staff
at
| FWHN advised me that I was going to be made a "project". This style
technique
| was disabled by the server within two months.
| 2. Next, I created theme sites on my local disc and applied those to
| www.mountainclubs.bc.ca with fair results. Initially, it was possible to
| effect change using User Defined styles, but eventually my "project"
status
| reduced effective design to styling only HTML Tags styles. And then that
was
| impossible.
| 3. In the final stage, I was making theme changes only when they were
| effected on my hard disc and saved as a unique theme name, and then the
new
| theme was applied to my site pages. Although beginning last week, it
seems
| that FWHN is disabling even this basic theme management. With the noted
| destruction of site tect and image content.
|
| Naturally, servicing 5,000 people my design response to legitimate
requests
| was initially extensive. Now it appears that SharePoint is being made
into a
| single style "template". Is my "project" status a universal woe?
|
| How much of the decay in FrontPage design functionality is related to
| whatever FWHN is attempting to accomplish with its "project", and how
much is
| related to problems with FrontPage 2003? FWHN tells me they have to
continue
| their "project" because "you are making life difficult for us".
|
| Is FrontPage really causing too many problems for servers? FrontPage
2003 is
| the only Office 2003 product without any significant (or specific)
product
| updates since its release 3 years ago. Is a solution for virtual
SharePoint
| accounts on the way. Incidentally, I left bCentral.com SharePoint
hosting
| months ago to escape even worse theme problems.
|
| My hope is that we will all get back the ability to use FontPage to
style
| our SharePoint sites. This is a corporate imperative. My hope is that
servers
| will not be able to make any customer into a "project" to attack
FrontPage
| functionality. My fear is that Microsoft will adopt the FWHN project
| directions and remove themes and styles from the FrontPage functionality
for
| SharePoint design. As Javascript is already disabled on the Tools, Page
| Options, Authoring tab when SharePoint is selected, this would
constitute a
| major deprecation of an essentially magnificent web design tool.
|
| Is there a safe and secure way to style sharePoint sites using FrontPage
| 2003 without server interference?
|
| ((this article is duplicated in the FrontPage Server Extensions forum))

 

[Murray]

Change hosts?

--
Murray
--------------
MVP Front Page

Stefan B Rusynko,

You have not answered my question. It's not that the host has the roles
set wrong. The host is deliberately tracking my styling efforts and
resetting roles to block the text book methods I am using to style my
sites using FrontPage 2003! Actually, at times it appears to be far more
delinquent than that. Is this being done for Microsoft? Rediculous,
right?. The host says I have to pay more if I want to do more. But hey! We
are following the book! The host is deliberately tracking and attacking my
code one plus years! Is there some code of ethics attached to this? Why
did Microsoft design software and direct it's servers to attack user code?
Where do we turn for support about this rather unpleasant FrontPage
problem?

My question is very simple. Is there a way to get past predatory host
obstruction of basic FrontPage functionality?

===PARTICULARS===

I am [strategically] applying style to Windows SharePoint Services sites,
using many methods detailed in Microsoft Press publications for WSS. My
sites are on Front Pages Web Hosting, a Microsoft recommended FrontPage
host. Everytime I get something working, my host deliberately disables my
code and the method I used to apply style to the site. The code works for
a while and then, suddenly I cannot reapply style to my suddenly messed
site using the same method. Kirk Duanes (as far as I know the only
technician at FWHN) tells me, "I am going to have to do this beacuse you
are on a virtual shared server and you are going to wreck everbody else's
site if something doesn't happen." He refuses to elaborate, telling me,
"You are too stupid to understand."

Design schedule is directly related to site stability. Daytimes are hell:
when I set proper class and ID attributes something or someone is deleting
or moving my attributes to other tables and objects on the page. and
otherwise making a mess of my pages. Some days. while I am working every
5-15 minutes my code is attacked. The attack frequently seriously disables
my site so I have to call support where I am always routed to Kirk. (I
thought FWHN was a big company.) When i create style sheets and apply the
changes after hours, the attack takes far longer to appear: it takes one
day to several months for the code attack to occur. Then the method I used
is blocked and my site is messed up. I keep asking myself, why would a
Microsoft recommended host be doing this? Or is this Kirk individual
attacking us on his own and somehow writing server rules for just our
site? I have advised Kirk that certain aspects of our site are a life and
death matter, so I find it difficult to believe anyone would obstruct us
so callously.

I am a web designer, not a secretary. I am not-for-profit but I do
legitimate work - e.g., a project with the national government to reduce
avalanche deaths. Last week three more deaths, one European and two
Candian fatalities. I consider, should we take action in court, make an
international noise? That might be easy, but we don't want to damage
Microsoft, do we? We are using FWHN for cost reasons. We keep hoping for
improvement in service, and looking for ways to bypass the
[[[UNADVERTISED]]] style for cost excuses that Kirk imposes on us. "What
can we do, Kirk?" "Oh, I'm not sure. We'll have to wait and see." The very
same question and answer every month for a year.

Is FWHN moving on to Expressions? So I check out Expressions Web Designer
on http://mountainclubs.ca and note that after one or two site entries my
login is permanently fried, even after I uninstall Expressions and return
to FWHN's butchered FrontPage. Another chat with Kirk, of course. I want
to challenge Kirk about the Expressions platform and the apparentlly
backwards direction being taken by the anti-style FWHN he has served up
for us. But then I am again wondering why I am always talking to Kirk and
realizing it could be weeks or months befor it is safe to touch our site
at night. Oops! By then my login will be lost; I'll email support - and
we'll end up in another chat with ...Kirk.

My question is very simple. Is there a way to get past predatory host
obstruction of basic FrontPage functionality? Perhaps some script that
conceals frontpage aspects of code from the server. A way to develop the
site but trick the server into not noticing any change to site structure?
The world I service deserves to benefit from and enjoy site design the way
FrontPage is designed to deliver it. Lawyer, heart-to-heart, script
intervention - what do we do? Are there affordable servers out there who
actually let you design without any interference?

Regs, mark.stewart

cc Executive Director, The Federation of Mountain Clubs of British
Columbia

If you are being blocked from using / changing themes on a WSS server
- the host does not have the roles set correctly
(or you do not have Web Designer or Administrator rights)
-
http://www.microsoft.com/resources/documentation/wss/2/all/adminguide/en-us/stsf01.mspx?mfr=true
Also see
http://www.sharepointcustomization.com/resources/tipstricks/wss_cssguide.htm
--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
_____________________________________________


| http://sbrenjoy.bizland.com/frontpage/themes/newthemes.html#Granular
|
| The link above describes how vbs can manipulate styles, and makes me
wonder
| if my virtual SharePoint host is manipulating my design by eliminating
all
| FrontPage style capability. My host is Front Pages Web Hosting, and I
thought
| by its name and Microsoft lables everywhere that it would support the
| FrontPage product on its SharePoint servers.
|
| One of my sites is http://www.mountainclubs.bc.ca and services about
5,000
| registered users. Due to ongoing problems fitting design to
organizational
| requests, the site is none too popular. The situation is that Front
Pages Web
| Hosting has questioned me for months about using FrontPage Theme
| customization. Beginning last week, any attempt I make to customize a
theme
| is completely ignored. In fact, not only are theme changes undone, but
all
| new related web part page content is deleted along with the theme
change!
|
| FWHN refers to my theme work as their "project". Here's how my theme
| "project" had to progress.
| 1. Initial success was had simply creating/editing a user defined style
with
| www.mountainclubs.bc.ca open in FrontPage. This is when techniical
staff at
| FWHN advised me that I was going to be made a "project". This style
technique
| was disabled by the server within two months.
| 2. Next, I created theme sites on my local disc and applied those to
| www.mountainclubs.bc.ca with fair results. Initially, it was possible
to
| effect change using User Defined styles, but eventually my "project"
status
| reduced effective design to styling only HTML Tags styles. And then
that was
| impossible.
| 3. In the final stage, I was making theme changes only when they were
| effected on my hard disc and saved as a unique theme name, and then the
new
| theme was applied to my site pages. Although beginning last week, it
seems
| that FWHN is disabling even this basic theme management. With the noted
| destruction of site tect and image content.
|
| Naturally, servicing 5,000 people my design response to legitimate
requests
| was initially extensive. Now it appears that SharePoint is being made
into a
| single style "template". Is my "project" status a universal woe?
|
| How much of the decay in FrontPage design functionality is related to
| whatever FWHN is attempting to accomplish with its "project", and how
much is
| related to problems with FrontPage 2003? FWHN tells me they have to
continue
| their "project" because "you are making life difficult for us".
|
| Is FrontPage really causing too many problems for servers? FrontPage
2003 is
| the only Office 2003 product without any significant (or specific)
product
| updates since its release 3 years ago. Is a solution for virtual
SharePoint
| accounts on the way. Incidentally, I left bCentral.com SharePoint
hosting
| months ago to escape even worse theme problems.
|
| My hope is that we will all get back the ability to use FontPage to
style
| our SharePoint sites. This is a corporate imperative. My hope is that
servers
| will not be able to make any customer into a "project" to attack
FrontPage
| functionality. My fear is that Microsoft will adopt the FWHN project
| directions and remove themes and styles from the FrontPage
functionality for
| SharePoint design. As Javascript is already disabled on the Tools, Page
| Options, Authoring tab when SharePoint is selected, this would
constitute a
| major deprecation of an essentially magnificent web design tool.
|
| Is there a safe and secure way to style sharePoint sites using
FrontPage
| 2003 without server interference?
|
| ((this article is duplicated in the FrontPage Server Extensions forum))

 

[Kevin Spencer]

My question is very simple. Is there a way to get past predatory host

obstruction of basic FrontPage functionality?

Your question is not as simple as you seem to think.

First, "Front Pages Web Hosting" is *not* a "Microsoft recommended FrontPage
host." In fact, there is no mention of this company anywhere on the
Microsoft web site, and almost none on Google. See
http://www.google.com/search?hl=en&q="Front+Pages+Web+Hosting" where I
was able to find precisely *five* references to this company. That means
that they are not "a big company." The fact that you thought that "by its
name and Microsoft lables everywhere that it would support the
FrontPage product on its SharePoint servers" is no indication that you are
correct in your conclusion. In fact, it is only an indication that the
company knows how to market itself to people like yourself. This company is
not part of Microsoft, and any dealings that you have with it do not involve
Microsoft in any way. So, if you feel that you should have an adversarial
relationship with this company, have no fear that you are affecting
Microsoft in any way.

That said, it sounds to me like the support person was telling you the truth
for the most part. If you have paid for a Virtual Server, your site is
probably indeed sharing components with other sites using the same web
server in one way or another. What I find curious is that you have been
granted permission to make changes that affect any of these other sites. The
following Microsoft reference details what is shared in such a
configuration:

http://www.microsoft.com/resources/documentation/wss/2/all/adminguide/en-us/stse02.mspx

The following Microsoft reference deals directly with Web Part
administration:

http://www.microsoft.com/resources/documentation/wss/2/all/adminguide/en-us/stswp03.mspx

Now, you may (or may not) have been a victim of misleading marketing by this
hosting company. In any case, you may indeed need a dedicated server in
order to control all aspects of your SharePoint site. Whether you want to
upgrade with your current company or find another one is up to you. But you
will probably find that it costs more than you're currently paying in any
case.

--
HTH,

Kevin Spencer
Microsoft MVP
Professional Numbskull

This is, by definition, not that.

Stefan B Rusynko,

You have not answered my question. It's not that the host has the roles
set wrong. The host is deliberately tracking my styling efforts and
resetting roles to block the text book methods I am using to style my
sites using FrontPage 2003! Actually, at times it appears to be far more
delinquent than that. Is this being done for Microsoft? Rediculous,
right?. The host says I have to pay more if I want to do more. But hey! We
are following the book! The host is deliberately tracking and attacking my
code one plus years! Is there some code of ethics attached to this? Why
did Microsoft design software and direct it's servers to attack user code?
Where do we turn for support about this rather unpleasant FrontPage
problem?

My question is very simple. Is there a way to get past predatory host
obstruction of basic FrontPage functionality?

===PARTICULARS===

I am [strategically] applying style to Windows SharePoint Services sites,
using many methods detailed in Microsoft Press publications for WSS. My
sites are on Front Pages Web Hosting, a Microsoft recommended FrontPage
host. Everytime I get something working, my host deliberately disables my
code and the method I used to apply style to the site. The code works for
a while and then, suddenly I cannot reapply style to my suddenly messed
site using the same method. Kirk Duanes (as far as I know the only
technician at FWHN) tells me, "I am going to have to do this beacuse you
are on a virtual shared server and you are going to wreck everbody else's
site if something doesn't happen." He refuses to elaborate, telling me,
"You are too stupid to understand."

Design schedule is directly related to site stability. Daytimes are hell:
when I set proper class and ID attributes something or someone is deleting
or moving my attributes to other tables and objects on the page. and
otherwise making a mess of my pages. Some days. while I am working every
5-15 minutes my code is attacked. The attack frequently seriously disables
my site so I have to call support where I am always routed to Kirk. (I
thought FWHN was a big company.) When i create style sheets and apply the
changes after hours, the attack takes far longer to appear: it takes one
day to several months for the code attack to occur. Then the method I used
is blocked and my site is messed up. I keep asking myself, why would a
Microsoft recommended host be doing this? Or is this Kirk individual
attacking us on his own and somehow writing server rules for just our
site? I have advised Kirk that certain aspects of our site are a life and
death matter, so I find it difficult to believe anyone would obstruct us
so callously.

I am a web designer, not a secretary. I am not-for-profit but I do
legitimate work - e.g., a project with the national government to reduce
avalanche deaths. Last week three more deaths, one European and two
Candian fatalities. I consider, should we take action in court, make an
international noise? That might be easy, but we don't want to damage
Microsoft, do we? We are using FWHN for cost reasons. We keep hoping for
improvement in service, and looking for ways to bypass the
[[[UNADVERTISED]]] style for cost excuses that Kirk imposes on us. "What
can we do, Kirk?" "Oh, I'm not sure. We'll have to wait and see." The very
same question and answer every month for a year.

Is FWHN moving on to Expressions? So I check out Expressions Web Designer
on http://mountainclubs.ca and note that after one or two site entries my
login is permanently fried, even after I uninstall Expressions and return
to FWHN's butchered FrontPage. Another chat with Kirk, of course. I want
to challenge Kirk about the Expressions platform and the apparentlly
backwards direction being taken by the anti-style FWHN he has served up
for us. But then I am again wondering why I am always talking to Kirk and
realizing it could be weeks or months befor it is safe to touch our site
at night. Oops! By then my login will be lost; I'll email support - and
we'll end up in another chat with ...Kirk.

My question is very simple. Is there a way to get past predatory host
obstruction of basic FrontPage functionality? Perhaps some script that
conceals frontpage aspects of code from the server. A way to develop the
site but trick the server into not noticing any change to site structure?
The world I service deserves to benefit from and enjoy site design the way
FrontPage is designed to deliver it. Lawyer, heart-to-heart, script
intervention - what do we do? Are there affordable servers out there who
actually let you design without any interference?

Regs, mark.stewart

cc Executive Director, The Federation of Mountain Clubs of British
Columbia

If you are being blocked from using / changing themes on a WSS server
- the host does not have the roles set correctly
(or you do not have Web Designer or Administrator rights)
-
http://www.microsoft.com/resources/documentation/wss/2/all/adminguide/en-us/stsf01.mspx?mfr=true
Also see
http://www.sharepointcustomization.com/resources/tipstricks/wss_cssguide.htm
--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
_____________________________________________


| http://sbrenjoy.bizland.com/frontpage/themes/newthemes.html#Granular
|
| The link above describes how vbs can manipulate styles, and makes me
wonder
| if my virtual SharePoint host is manipulating my design by eliminating
all
| FrontPage style capability. My host is Front Pages Web Hosting, and I
thought
| by its name and Microsoft lables everywhere that it would support the
| FrontPage product on its SharePoint servers.
|
| One of my sites is http://www.mountainclubs.bc.ca and services about
5,000
| registered users. Due to ongoing problems fitting design to
organizational
| requests, the site is none too popular. The situation is that Front
Pages Web
| Hosting has questioned me for months about using FrontPage Theme
| customization. Beginning last week, any attempt I make to customize a
theme
| is completely ignored. In fact, not only are theme changes undone, but
all
| new related web part page content is deleted along with the theme
change!
|
| FWHN refers to my theme work as their "project". Here's how my theme
| "project" had to progress.
| 1. Initial success was had simply creating/editing a user defined style
with
| www.mountainclubs.bc.ca open in FrontPage. This is when techniical
staff at
| FWHN advised me that I was going to be made a "project". This style
technique
| was disabled by the server within two months.
| 2. Next, I created theme sites on my local disc and applied those to
| www.mountainclubs.bc.ca with fair results. Initially, it was possible
to
| effect change using User Defined styles, but eventually my "project"
status
| reduced effective design to styling only HTML Tags styles. And then
that was
| impossible.
| 3. In the final stage, I was making theme changes only when they were
| effected on my hard disc and saved as a unique theme name, and then the
new
| theme was applied to my site pages. Although beginning last week, it
seems
| that FWHN is disabling even this basic theme management. With the noted
| destruction of site tect and image content.
|
| Naturally, servicing 5,000 people my design response to legitimate
requests
| was initially extensive. Now it appears that SharePoint is being made
into a
| single style "template". Is my "project" status a universal woe?
|
| How much of the decay in FrontPage design functionality is related to
| whatever FWHN is attempting to accomplish with its "project", and how
much is
| related to problems with FrontPage 2003? FWHN tells me they have to
continue
| their "project" because "you are making life difficult for us".
|
| Is FrontPage really causing too many problems for servers? FrontPage
2003 is
| the only Office 2003 product without any significant (or specific)
product
| updates since its release 3 years ago. Is a solution for virtual
SharePoint
| accounts on the way. Incidentally, I left bCentral.com SharePoint
hosting
| months ago to escape even worse theme problems.
|
| My hope is that we will all get back the ability to use FontPage to
style
| our SharePoint sites. This is a corporate imperative. My hope is that
servers
| will not be able to make any customer into a "project" to attack
FrontPage
| functionality. My fear is that Microsoft will adopt the FWHN project
| directions and remove themes and styles from the FrontPage
functionality for
| SharePoint design. As Javascript is already disabled on the Tools, Page
| Options, Authoring tab when SharePoint is selected, this would
constitute a
| major deprecation of an essentially magnificent web design tool.
|
| Is there a safe and secure way to style sharePoint sites using
FrontPage
| 2003 without server interference?
|
| ((this article is duplicated in the FrontPage Server Extensions forum))

 

[Rob Giordano \(Crash\)]

buy more tinfoil?


| Change hosts?
|
| --
| Murray
| --------------
| MVP Front Page
|
|
| | > Stefan B Rusynko,
| >
| > You have not answered my question. It's not that the host has the roles
| > set wrong. The host is deliberately tracking my styling efforts and
| > resetting roles to block the text book methods I am using to style my
| > sites using FrontPage 2003! Actually, at times it appears to be far more
| > delinquent than that. Is this being done for Microsoft? Rediculous,
| > right?. The host says I have to pay more if I want to do more. But hey!
We
| > are following the book! The host is deliberately tracking and attacking
my
| > code one plus years! Is there some code of ethics attached to this? Why
| > did Microsoft design software and direct it's servers to attack user
code?
| > Where do we turn for support about this rather unpleasant FrontPage
| > problem?
| >
| > My question is very simple. Is there a way to get past predatory host
| > obstruction of basic FrontPage functionality?
| >
| > ===PARTICULARS===
| >
| > I am [strategically] applying style to Windows SharePoint Services
sites,
| > using many methods detailed in Microsoft Press publications for WSS. My
| > sites are on Front Pages Web Hosting, a Microsoft recommended FrontPage
| > host. Everytime I get something working, my host deliberately disables
my
| > code and the method I used to apply style to the site. The code works
for
| > a while and then, suddenly I cannot reapply style to my suddenly messed
| > site using the same method. Kirk Duanes (as far as I know the only
| > technician at FWHN) tells me, "I am going to have to do this beacuse you
| > are on a virtual shared server and you are going to wreck everbody
else's
| > site if something doesn't happen." He refuses to elaborate, telling me,
| > "You are too stupid to understand."
| >
| > Design schedule is directly related to site stability. Daytimes are
hell:
| > when I set proper class and ID attributes something or someone is
deleting
| > or moving my attributes to other tables and objects on the page. and
| > otherwise making a mess of my pages. Some days. while I am working every
| > 5-15 minutes my code is attacked. The attack frequently seriously
disables
| > my site so I have to call support where I am always routed to Kirk. (I
| > thought FWHN was a big company.) When i create style sheets and apply
the
| > changes after hours, the attack takes far longer to appear: it takes one
| > day to several months for the code attack to occur. Then the method I
used
| > is blocked and my site is messed up. I keep asking myself, why would a
| > Microsoft recommended host be doing this? Or is this Kirk individual
| > attacking us on his own and somehow writing server rules for just our
| > site? I have advised Kirk that certain aspects of our site are a life
and
| > death matter, so I find it difficult to believe anyone would obstruct us
| > so callously.
| >
| > I am a web designer, not a secretary. I am not-for-profit but I do
| > legitimate work - e.g., a project with the national government to reduce
| > avalanche deaths. Last week three more deaths, one European and two
| > Candian fatalities. I consider, should we take action in court, make an
| > international noise? That might be easy, but we don't want to damage
| > Microsoft, do we? We are using FWHN for cost reasons. We keep hoping for
| > improvement in service, and looking for ways to bypass the
| > [[[UNADVERTISED]]] style for cost excuses that Kirk imposes on us. "What
| > can we do, Kirk?" "Oh, I'm not sure. We'll have to wait and see." The
very
| > same question and answer every month for a year.
| >
| > Is FWHN moving on to Expressions? So I check out Expressions Web
Designer
| > on http://mountainclubs.ca and note that after one or two site entries
my
| > login is permanently fried, even after I uninstall Expressions and
return
| > to FWHN's butchered FrontPage. Another chat with Kirk, of course. I want
| > to challenge Kirk about the Expressions platform and the apparentlly
| > backwards direction being taken by the anti-style FWHN he has served up
| > for us. But then I am again wondering why I am always talking to Kirk
and
| > realizing it could be weeks or months befor it is safe to touch our site
| > at night. Oops! By then my login will be lost; I'll email support - and
| > we'll end up in another chat with ...Kirk.
| >
| > My question is very simple. Is there a way to get past predatory host
| > obstruction of basic FrontPage functionality? Perhaps some script that
| > conceals frontpage aspects of code from the server. A way to develop the
| > site but trick the server into not noticing any change to site
structure?
| > The world I service deserves to benefit from and enjoy site design the
way
| > FrontPage is designed to deliver it. Lawyer, heart-to-heart, script
| > intervention - what do we do? Are there affordable servers out there who
| > actually let you design without any interference?
| >
| > Regs, mark.stewart
| >
| > cc Executive Director, The Federation of Mountain Clubs of British
| > Columbia
| >
| > "Stefan B Rusynko" wrote:
| >
| >> If you are being blocked from using / changing themes on a WSS server
| >> - the host does not have the roles set correctly
| >> (or you do not have Web Designer or Administrator rights)
| >> -
| >>
http://www.microsoft.com/resources/documentation/wss/2/all/adminguide/en-us/stsf01.mspx?mfr=true
| >> Also see
| >>
http://www.sharepointcustomization.com/resources/tipstricks/wss_cssguide.htm
| >> --
| >>
| >> _____________________________________________
| >> SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
| >> "Warning - Using the F1 Key will not break anything!" (-;
| >> To find the best Newsgroup for FrontPage support see:
| >>
http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
| >> _____________________________________________
| >>
| >>
| >> | >> | http://sbrenjoy.bizland.com/frontpage/themes/newthemes.html#Granular
| >> |
| >> | The link above describes how vbs can manipulate styles, and makes me
| >> wonder
| >> | if my virtual SharePoint host is manipulating my design by
eliminating
| >> all
| >> | FrontPage style capability. My host is Front Pages Web Hosting, and I
| >> thought
| >> | by its name and Microsoft lables everywhere that it would support the
| >> | FrontPage product on its SharePoint servers.
| >> |
| >> | One of my sites is http://www.mountainclubs.bc.ca and services about
| >> 5,000
| >> | registered users. Due to ongoing problems fitting design to
| >> organizational
| >> | requests, the site is none too popular. The situation is that Front
| >> Pages Web
| >> | Hosting has questioned me for months about using FrontPage Theme
| >> | customization. Beginning last week, any attempt I make to customize a
| >> theme
| >> | is completely ignored. In fact, not only are theme changes undone,
but
| >> all
| >> | new related web part page content is deleted along with the theme
| >> change!
| >> |
| >> | FWHN refers to my theme work as their "project". Here's how my theme
| >> | "project" had to progress.
| >> | 1. Initial success was had simply creating/editing a user defined
style
| >> with
| >> | www.mountainclubs.bc.ca open in FrontPage. This is when techniical
| >> staff at
| >> | FWHN advised me that I was going to be made a "project". This style
| >> technique
| >> | was disabled by the server within two months.
| >> | 2. Next, I created theme sites on my local disc and applied those to
| >> | www.mountainclubs.bc.ca with fair results. Initially, it was possible
| >> to
| >> | effect change using User Defined styles, but eventually my "project"
| >> status
| >> | reduced effective design to styling only HTML Tags styles. And then
| >> that was
| >> | impossible.
| >> | 3. In the final stage, I was making theme changes only when they were
| >> | effected on my hard disc and saved as a unique theme name, and then
the
| >> new
| >> | theme was applied to my site pages. Although beginning last week, it
| >> seems
| >> | that FWHN is disabling even this basic theme management. With the
noted
| >> | destruction of site tect and image content.
| >> |
| >> | Naturally, servicing 5,000 people my design response to legitimate
| >> requests
| >> | was initially extensive. Now it appears that SharePoint is being made
| >> into a
| >> | single style "template". Is my "project" status a universal woe?
| >> |
| >> | How much of the decay in FrontPage design functionality is related to
| >> | whatever FWHN is attempting to accomplish with its "project", and how
| >> much is
| >> | related to problems with FrontPage 2003? FWHN tells me they have to
| >> continue
| >> | their "project" because "you are making life difficult for us".
| >> |
| >> | Is FrontPage really causing too many problems for servers? FrontPage
| >> 2003 is
| >> | the only Office 2003 product without any significant (or specific)
| >> product
| >> | updates since its release 3 years ago. Is a solution for virtual
| >> SharePoint
| >> | accounts on the way. Incidentally, I left bCentral.com SharePoint
| >> hosting
| >> | months ago to escape even worse theme problems.
| >> |
| >> | My hope is that we will all get back the ability to use FontPage to
| >> style
| >> | our SharePoint sites. This is a corporate imperative. My hope is that
| >> servers
| >> | will not be able to make any customer into a "project" to attack
| >> FrontPage
| >> | functionality. My fear is that Microsoft will adopt the FWHN project
| >> | directions and remove themes and styles from the FrontPage
| >> functionality for
| >> | SharePoint design. As Javascript is already disabled on the Tools,
Page
| >> | Options, Authoring tab when SharePoint is selected, this would
| >> constitute a
| >> | major deprecation of an essentially magnificent web design tool.
| >> |
| >> | Is there a safe and secure way to style sharePoint sites using
| >> FrontPage
| >> | 2003 without server interference?
| >> |
| >> | ((this article is duplicated in the FrontPage Server Extensions
forum))
| >>
| >>
| >>
| >
|
|

 

[Stefan B Rusynko]

See my response to your other duplicate thread

--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
_____________________________________________


| Stefan B Rusynko,
|
| You have not answered my question. It's not that the host has the roles set
| wrong. The host is deliberately tracking my styling efforts and resetting
| roles to block the text book methods I am using to style my sites using
| FrontPage 2003! Actually, at times it appears to be far more delinquent than
| that. Is this being done for Microsoft? Rediculous, right?. The host says I
| have to pay more if I want to do more. But hey! We are following the book!
| The host is deliberately tracking and attacking my code one plus years! Is
| there some code of ethics attached to this? Why did Microsoft design
| software and direct it's servers to attack user code? Where do we turn for
| support about this rather unpleasant FrontPage problem?
|
| My question is very simple. Is there a way to get past predatory host
| obstruction of basic FrontPage functionality?
|
| ===PARTICULARS===
|
| I am [strategically] applying style to Windows SharePoint Services sites,
| using many methods detailed in Microsoft Press publications for WSS. My
| sites are on Front Pages Web Hosting, a Microsoft recommended FrontPage
| host. Everytime I get something working, my host deliberately disables my
| code and the method I used to apply style to the site. The code works for a
| while and then, suddenly I cannot reapply style to my suddenly messed site
| using the same method. Kirk Duanes (as far as I know the only technician at
| FWHN) tells me, "I am going to have to do this beacuse you are on a virtual
| shared server and you are going to wreck everbody else's site if something
| doesn't happen." He refuses to elaborate, telling me, "You are too stupid to
| understand."
|
| Design schedule is directly related to site stability. Daytimes are hell:
| when I set proper class and ID attributes something or someone is deleting
| or moving my attributes to other tables and objects on the page. and
| otherwise making a mess of my pages. Some days. while I am working every
| 5-15 minutes my code is attacked. The attack frequently seriously disables
| my site so I have to call support where I am always routed to Kirk. (I
| thought FWHN was a big company.) When i create style sheets and apply the
| changes after hours, the attack takes far longer to appear: it takes one day
| to several months for the code attack to occur. Then the method I used is
| blocked and my site is messed up. I keep asking myself, why would a
| Microsoft recommended host be doing this? Or is this Kirk individual
| attacking us on his own and somehow writing server rules for just our site?
| I have advised Kirk that certain aspects of our site are a life and death
| matter, so I find it difficult to believe anyone would obstruct us so
| callously.
|
| I am a web designer, not a secretary. I am not-for-profit but I do
| legitimate work - e.g., a project with the national government to reduce
| avalanche deaths. Last week three more deaths, one European and two Candian
| fatalities. I consider, should we take action in court, make an
| international noise? That might be easy, but we don't want to damage
| Microsoft, do we? We are using FWHN for cost reasons. We keep hoping for
| improvement in service, and looking for ways to bypass the
| [[[UNADVERTISED]]] style for cost excuses that Kirk imposes on us. "What can
| we do, Kirk?" "Oh, I'm not sure. We'll have to wait and see." The very same
| question and answer every month for a year.
|
| Is FWHN moving on to Expressions? So I check out Expressions Web Designer on
| http://mountainclubs.ca and note that after one or two site entries my login
| is permanently fried, even after I uninstall Expressions and return to
| FWHN's butchered FrontPage. Another chat with Kirk, of course. I want to
| challenge Kirk about the Expressions platform and the apparentlly backwards
| direction being taken by the anti-style FWHN he has served up for us. But
| then I am again wondering why I am always talking to Kirk and realizing it
| could be weeks or months befor it is safe to touch our site at night. Oops!
| By then my login will be lost; I'll email support - and we'll end up in
| another chat with ...Kirk.
|
| My question is very simple. Is there a way to get past predatory host
| obstruction of basic FrontPage functionality? Perhaps some script that
| conceals frontpage aspects of code from the server. A way to develop the
| site but trick the server into not noticing any change to site structure?
| The world I service deserves to benefit from and enjoy site design the way
| FrontPage is designed to deliver it. Lawyer, heart-to-heart, script
| intervention - what do we do? Are there affordable servers out there who
| actually let you design without any interference?
|
| Regs, mark.stewart
|
| cc Executive Director, The Federation of Mountain Clubs of British Columbia
|
| "Stefan B Rusynko" wrote:
|
| > If you are being blocked from using / changing themes on a WSS server
| > - the host does not have the roles set correctly
| > (or you do not have Web Designer or Administrator rights)
| > -
| > http://www.microsoft.com/resources/documentation/wss/2/all/adminguide/en-us/stsf01.mspx?mfr=true
| > Also see
| > http://www.sharepointcustomization.com/resources/tipstricks/wss_cssguide.htm
| > --
| >
| > _____________________________________________
| > SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
| > "Warning - Using the F1 Key will not break anything!" (-;
| > To find the best Newsgroup for FrontPage support see:
| > http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
| > _____________________________________________
| >
| >
| > | > | http://sbrenjoy.bizland.com/frontpage/themes/newthemes.html#Granular
| > |
| > | The link above describes how vbs can manipulate styles, and makes me
| > wonder
| > | if my virtual SharePoint host is manipulating my design by eliminating
| > all
| > | FrontPage style capability. My host is Front Pages Web Hosting, and I
| > thought
| > | by its name and Microsoft lables everywhere that it would support the
| > | FrontPage product on its SharePoint servers.
| > |
| > | One of my sites is http://www.mountainclubs.bc.ca and services about
| > 5,000
| > | registered users. Due to ongoing problems fitting design to
| > organizational
| > | requests, the site is none too popular. The situation is that Front
| > Pages Web
| > | Hosting has questioned me for months about using FrontPage Theme
| > | customization. Beginning last week, any attempt I make to customize a
| > theme
| > | is completely ignored. In fact, not only are theme changes undone, but
| > all
| > | new related web part page content is deleted along with the theme
| > change!
| > |
| > | FWHN refers to my theme work as their "project". Here's how my theme
| > | "project" had to progress.
| > | 1. Initial success was had simply creating/editing a user defined style
| > with
| > | www.mountainclubs.bc.ca open in FrontPage. This is when techniical staff
| > at
| > | FWHN advised me that I was going to be made a "project". This style
| > technique
| > | was disabled by the server within two months.
| > | 2. Next, I created theme sites on my local disc and applied those to
| > | www.mountainclubs.bc.ca with fair results. Initially, it was possible to
| > | effect change using User Defined styles, but eventually my "project"
| > status
| > | reduced effective design to styling only HTML Tags styles. And then that
| > was
| > | impossible.
| > | 3. In the final stage, I was making theme changes only when they were
| > | effected on my hard disc and saved as a unique theme name, and then the
| > new
| > | theme was applied to my site pages. Although beginning last week, it
| > seems
| > | that FWHN is disabling even this basic theme management. With the noted
| > | destruction of site tect and image content.
| > |
| > | Naturally, servicing 5,000 people my design response to legitimate
| > requests
| > | was initially extensive. Now it appears that SharePoint is being made
| > into a
| > | single style "template". Is my "project" status a universal woe?
| > |
| > | How much of the decay in FrontPage design functionality is related to
| > | whatever FWHN is attempting to accomplish with its "project", and how
| > much is
| > | related to problems with FrontPage 2003? FWHN tells me they have to
| > continue
| > | their "project" because "you are making life difficult for us".
| > |
| > | Is FrontPage really causing too many problems for servers? FrontPage
| > 2003 is
| > | the only Office 2003 product without any significant (or specific)
| > product
| > | updates since its release 3 years ago. Is a solution for virtual
| > SharePoint
| > | accounts on the way. Incidentally, I left bCentral.com SharePoint
| > hosting
| > | months ago to escape even worse theme problems.
| > |
| > | My hope is that we will all get back the ability to use FontPage to
| > style
| > | our SharePoint sites. This is a corporate imperative. My hope is that
| > servers
| > | will not be able to make any customer into a "project" to attack
| > FrontPage
| > | functionality. My fear is that Microsoft will adopt the FWHN project
| > | directions and remove themes and styles from the FrontPage functionality
| > for
| > | SharePoint design. As Javascript is already disabled on the Tools, Page
| > | Options, Authoring tab when SharePoint is selected, this would
| > constitute a
| > | major deprecation of an essentially magnificent web design tool.
| > |
| > | Is there a safe and secure way to style sharePoint sites using FrontPage
| > | 2003 without server interference?
| > |
| > | ((this article is duplicated in the FrontPage Server Extensions forum))
| >
| >
| >
|