CiviCRM Community Forums (archive)

Same problem here - can't get the widget working - the only think I can do is change colours.
No text appears. No progress bar.

You can see the widget in action here:

http://civicrm.org/participate/mih

drupal 7 / Civi 4.1.x

might want to compare and see how your site is different

lobo

I know this is an old thread, but just in case anyone else is looking for answers to why the text won't show up in the widget, for me it was an .htaccess restriction that was causing it. Seems absolutely logical now, but since it took me forever to figure it out, and I didn't see that come up as a solution in any of the posts I read I thought I would pass it on....

I got this from  my hosting service.   Posting in the hope it will help with 403 errors.

-----


The issue in this case was due to a Server Configuration that is defined within ModSecurity and its ruleset. Unfortunately, the rule sets in place are not available to view on the server end. If you do notice any type of errors, especially a 500 Internal Server or 403 Forbidden error, please let us know so that we can review the server logs for any issues related to this security feature that is in place.

ModSecurity is an open source, free web application firewall Apache module. ModSecurity is deployed to establish an external security layer that increases security, detects, and prevents attacks before they reach web applications. It
provides protection from a range of attacks against web applications and allows for HTTP traffic monitoring and real-time analysis.

In some instances, legitimate connections, script, or tools/applications can be blocked by ModSecurity rules attempted to defend the server. It is better to avoid adding exceptions to these rules that defend the server because most
mod_security problems can be resolved by changing how an application or plugin performs, modifying a script, or reducing the size of files uploaded to your account.

We can send a request for a ModSecurity exception up to our next level of support, but it is a request and must be approved before being implemented on any account. ModSecurity exceptions when added are specific to a directory or
file, and are not added to the entire account. Similarly, since exceptions are added by the rule, we cannot simply except a user's entire account from all ModSecurity rules. In essence, a specific rule running from a specific directory
or file must be triggered before we will be able to consider applying any exceptions to an account.