ProsePoint Express: hosted newspaper website content management software

Overcoming the "Clean URL" Problem

  • strict warning: Non-static method view::load() should not be called statically in /home/prosepoint.org/bzr/public_html/profiles/prosepoint/modules/views/views.module on line 879.
  • strict warning: Declaration of views_handler_argument::init() should be compatible with views_handler::init(&$view, $options) in /home/prosepoint.org/bzr/public_html/profiles/prosepoint/modules/views/handlers/views_handler_argument.inc on line 0.
  • strict warning: Declaration of views_handler_filter::options_validate() should be compatible with views_handler::options_validate($form, &$form_state) in /home/prosepoint.org/bzr/public_html/profiles/prosepoint/modules/views/handlers/views_handler_filter.inc on line 0.
  • strict warning: Declaration of views_handler_filter::options_submit() should be compatible with views_handler::options_submit($form, &$form_state) in /home/prosepoint.org/bzr/public_html/profiles/prosepoint/modules/views/handlers/views_handler_filter.inc on line 0.
  • strict warning: Declaration of views_handler_filter_node_status::operator_form() should be compatible with views_handler_filter::operator_form(&$form, &$form_state) in /home/prosepoint.org/bzr/public_html/profiles/prosepoint/modules/views/modules/node/views_handler_filter_node_status.inc on line 0.
  • strict warning: Non-static method view::load() should not be called statically in /home/prosepoint.org/bzr/public_html/profiles/prosepoint/modules/views/views.module on line 879.
  • strict warning: Declaration of views_handler_filter_boolean_operator::value_validate() should be compatible with views_handler_filter::value_validate($form, &$form_state) in /home/prosepoint.org/bzr/public_html/profiles/prosepoint/modules/views/handlers/views_handler_filter_boolean_operator.inc on line 0.
  • strict warning: Declaration of date_api_filter_handler::value_validate() should be compatible with views_handler_filter::value_validate($form, &$form_state) in /home/prosepoint.org/bzr/public_html/profiles/prosepoint/modules/date/includes/date_api_filter_handler.inc on line 0.
  • strict warning: Non-static method view::load() should not be called statically in /home/prosepoint.org/bzr/public_html/profiles/prosepoint/modules/views/views.module on line 879.
  • strict warning: Declaration of views_plugin_row::options_validate() should be compatible with views_plugin::options_validate(&$form, &$form_state) in /home/prosepoint.org/bzr/public_html/profiles/prosepoint/modules/views/plugins/views_plugin_row.inc on line 0.
  • strict warning: Declaration of views_plugin_row::options_submit() should be compatible with views_plugin::options_submit(&$form, &$form_state) in /home/prosepoint.org/bzr/public_html/profiles/prosepoint/modules/views/plugins/views_plugin_row.inc on line 0.
5 replies [Last post]
erjenkins1
User offline. Last seen 6 years 31 weeks ago. Offline
Joined: 09/04/2011
Posts:

Hello all. Trying to install ProsePoint and not having much luck. I'm getting stuck at the "Clean URLs" point, and the option to enable them is not available.

GoDaddy uses Apache and clean URLs are enabled. I even tried changing the .htaccess code to comment out the "Rewrite /" code, which apparently works for some people.

Is there a way to disable the requirement for clean urls, and then enable them in the Drupal administration module?

I've pasted the contents of my .htaccess file below (this is the default -- before I comment out the "Rewrite" function. Thank you for any help you can offer.

#

# Apache/PHP/Drupal settings:

#

 

# Protect files and directories from prying eyes.

<FilesMatch "\.(engine|inc|info|install|make|module|profile|test|po|sh|.*sql|theme|tpl(\.php)?|xtmpl|svn-base)$|^(code-style\.pl|Entries.*|Repository|Root|Tag|Template|all-wcprops|entries|format)$">

Order allow,deny

</FilesMatch>

 

# Don't show directory listings for URLs which map to a directory.

Options -Indexes

 

# Follow symbolic links in this directory.

Options +FollowSymLinks

 

# Make Drupal handle any 404 errors.

ErrorDocument 404 /index.php

 

# Force simple error message for requests for non-existent favicon.ico.

<Files favicon.ico>

# There is no end quote below, for compatibility with Apache 1.3.

ErrorDocument 404 "The requested file favicon.ico was not found.

</Files>

 

# Set the default handler.

DirectoryIndex index.php

 

# Override PHP settings. More in sites/default/settings.php

# but the following cannot be changed at runtime.

 

# PHP 4, Apache 1.

<IfModule mod_php4.c>

php_value magic_quotes_gpc                0

php_value register_globals                0

php_value session.auto_start              0

php_value mbstring.http_input             pass

php_value mbstring.http_output            pass

php_value mbstring.encoding_translation   0

</IfModule>

 

# PHP 4, Apache 2.

<IfModule sapi_apache2.c>

php_value magic_quotes_gpc                0

php_value register_globals                0

php_value session.auto_start              0

php_value mbstring.http_input             pass

php_value mbstring.http_output            pass

php_value mbstring.encoding_translation   0

</IfModule>

 

# PHP 5, Apache 1 and 2.

<IfModule mod_php5.c>

php_value magic_quotes_gpc                0

php_value register_globals                0

php_value session.auto_start              0

php_value mbstring.http_input             pass

php_value mbstring.http_output            pass

php_value mbstring.encoding_translation   0

</IfModule>

 

# Requires mod_expires to be enabled.

<IfModule mod_expires.c>

# Enable expirations.

ExpiresActive On

 

# Cache all files for 2 weeks after access (A).

ExpiresDefault A1209600

 

<FilesMatch \.php$>

# Do not allow PHP scripts to be cached unless they explicitly send cache

# headers themselves. Otherwise all scripts would have to overwrite the

# headers set by mod_expires if they want another caching behavior. This may

# fail if an error occurs early in the bootstrap process, and it may cause

# problems if a non-Drupal PHP file is installed in a subdirectory.

ExpiresActive Off

</FilesMatch>

</IfModule>

 

# Various rewrite rules.

<IfModule mod_rewrite.c>

RewriteEngine on

 

# If your site can be accessed both with and without the 'www.' prefix, you

# can use one of the following settings to redirect users to your preferred

# URL, either WITH or WITHOUT the 'www.' prefix. Choose ONLY one option:

#

# To redirect all users to access the site WITH the 'www.' prefix,

# (http://example.com/... will be redirected to http://www.example.com/...)

# adapt and uncomment the following:

# RewriteCond %{HTTP_HOST} ^example\.com$ [NC]

# RewriteRule ^(.*)$ http://www.example.com/$1 [L,R=301]

#

# To redirect all users to access the site WITHOUT the 'www.' prefix,

# (http://www.example.com/... will be redirected to http://example.com/...)

# uncomment and adapt the following:

# RewriteCond %{HTTP_HOST} ^www\.example\.com$ [NC]

# RewriteRule ^(.*)$ http://example.com/$1 [L,R=301]

 

# Modify the RewriteBase if you are using Drupal in a subdirectory or in a

# VirtualDocumentRoot and the rewrite rules are not working properly.

# For example if your site is at http://example.com/drupal uncomment and

# modify the following line:

# RewriteBase /

#

# If your site is running in a VirtualDocumentRoot at http://example.com/,

# uncomment the following line:

# RewriteBase /

 

# Rewrite URLs of the form 'x' to the form 'index.php?q=x'.

RewriteCond %{REQUEST_FILENAME} !-f

RewriteCond %{REQUEST_FILENAME} !-d

RewriteCond %{REQUEST_URI} !=/favicon.ico

RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]

</IfModule>

# $Id: .htaccess,v 1.90.2.5 2010/02/02 07:25:22 dries Exp $

 

 

beng
User offline. Last seen 4 years 31 weeks ago. Offline
Joined: 27/02/2009
Posts:
...

Hi,

Sorry. If clean urls are not enabled, some parts of ProsePoint (including the image handling) won't work. That's why it was made a requirement.

If you're installing in a subdirectory, you could try changing 'RewriteBase /' to 'RewriteBase <subdirectory>' and see if that helps.

Otherwise, I don't know. mod_rewrite is a standard component of Apache and it usually just works with default settings. You'd have to ask your hosting provider to chase it up.

erjenkins1
User offline. Last seen 6 years 31 weeks ago. Offline
Joined: 09/04/2011
Posts:
Do you mean if I'm trying to
Do you mean if I'm trying to install ProsePoint on a subdirectory of the server, or a subdirectory of the domain? Because I'm on a shared server, PP is going in a subfolder that's connected with another domain. I'm going to try that and will keep you updated.
beng
User offline. Last seen 4 years 31 weeks ago. Offline
Joined: 27/02/2009
Posts:
...

If ProsePoint is installed into a url which is a subdirectory of something else, then you may need to change the RewriteBase in .htaccess.

However, I don't know how this interacts with GoDaddy's scheme of having subdomains urls stored in a filesystem subdirectory of the root domain. That's why I'd suggest you ask them.

erjenkins1
User offline. Last seen 6 years 31 weeks ago. Offline
Joined: 09/04/2011
Posts:
Hello. I'm revisiting this

Hello. I'm revisiting this issue. I have no trouble installing Drupal 6 and getting past the "Clean URL" section (and enabling them). I'm wondering why it's different with ProsePoint when I've followed the same directions.

Any clue?

erjenkins1
User offline. Last seen 6 years 31 weeks ago. Offline
Joined: 09/04/2011
Posts:
Fixed

Just for future reference, I fixed the problem. Although I could not get past the "Clean URL test" at installation, I was able to easily enable the feature in the "Site Configuration" settings.

First, I had to comment out the code that requires the Clean URL test at installation. Once the program was actually installed, the option to enable the clean urls was available in the admin panel. There's apparently a problem with the clean url test and shared servers, or something of that nature.

Thanks!