is there a way of no url rewrite

[haha]

I;m using apache and i always catch with 500 error. and i 'm searching for a way that without url rewrite. is it there ? maybe it would solve my problem

i've try the ways of comment or uncomment in .htaccess.

[Macrura]

@haha, AFAIK processwire requires URL rewriting with apache.

[adrian]

Macrura is correct - PW needs mod rewrite. Don't give up so easily on the 500 error - there are lots of possible causes of this and lots of easy fixes - you just need to figure out which one is the issue with your particular hosting environment. If you have tried all the rewrite base options, including matching it to the path of your site on the server, then you might next try:

#SetEnv HTTP_MOD_REWRITE On

http://processwire.com/talk/topic/1962-cant-reach-admin-page/?p=49524

Or this:

http://processwire.com/talk/topic/2439-htaccess-issue/?p=39674

If that doesn't work, take a look through these search results:

https://www.google.com/search?q=site%3Aprocesswire.com+500+error&oq=site

I am sure we can help you figure it out.

[teppo]

Macrura is right -- mod_rewrite is essential for ProcessWire to function properly. Short answer is "it's not doable".

Regarding your actual issue here, there are multiple notes about various possible 500 errors in ProcessWire's .htaccess file. If you're getting these errors, take a close look at that file and see if any of those tips can help you. If not, try posting more details here and we'll do our best to help you with this.

Longer answer is that even if you could tweak ProcessWire to function without mod_rewrite, it would come with two huge drawbacks (that I can think of right now):

• your URLs would be like example.com/?it=/about/site/ instead of example.com/about/site/
• you'd be compromising a lot of security features, such as protected directories and files

Possibly even bigger issue would be that ProcessWire really isn't intended to work like that. Internal links, URLs and things like that are very likely to break here and there. In a nutshell: trust me, this is not a good idea.

[haha]

@adrian  it's so hard to figure it out i have tried the methods you gave it to me.

then i don't know where to locate the reason of the problem.

[kongondo]

@adrian  it's so hard to figure it out i have tried the methods you gave it to me.

then i don't know where to locate the reason of the problem.

Is this a shared host? Sometimes its just easier to ask your host provider to have a look and tell you what settings on their servers do not like your .htaccess rules, and which rules in particular...