8

Thanks for nudge Derek. I was totally unaware that the site was running as a FastCGI process. This is the default with (mt) dv 4.0 & Plesk 11.0.9 when creating new hosts. Which maybe explains other user's issues with removing index.php at MediaTemple I switched it back to Apache and removed the ? from the rewrite rule and the redirects are working ...


4

If you are using EE 2.7+ there is a new current_query_string global variable you can test against. {if current_query_string} {redirect="404"} {/if} Or, for versions less than EE 2.7... Install the Mo Variables Extension and enable the setting that gives you a {query_string} variable. Then in your homepage template you can do {if query_string} {...


3

Shouldn't it be t.author_id instead of t.author? {exp:query sql=" SELECT count(*) AS num_members FROM exp_members m JOIN exp_channel_titles t on t.author_id = m.member_id"} {num_members} {/exp:query}


3

I don't think the issue is with the friendly URL's, however you can test this by removing that block from the htaccess and typing the index.php part into your URL : http://www.example.com/index.php?foo=bar Another thing to check is that ExpressionEngine itself is not clearing the get parameters, which can happen as all ee actions are submitted to the home ...


3

You'll need an add-on for this. Mo’ Variables is a good option. {get:url} Maybe you should rename your variable. "url" is too common and it can create some conflicts.


2

I'm assuming you're referring to EE 2.8 layouts. It isn't possible to process layouts within a plugin or module tags so using an if statement or Switchee isn't going to work within the template itself. However you could use something like Switchee as Jean St-Amand mentioned within the layout to provide variations of that layout depending on the string. ...


2

Seems like you ought to be able to handle it with switchee using regex to determine which layout scenario is present in your URL, for example. I'm not a regex wiz so I won't pretend to know what patterns you would need - but it's switch case logic coupled with its support for regex is what made me think of it as a possible answer for you.


2

I'm not sure of this behavior being applied to other fields than comments, but maybe it worth to try. On Control Panel > Admin > Security and Privacy > Security and Sessions, look for Apply Rank Denial to User-submitted Links.


1

Thank you for adding more information in question: The answer is "YES", You can remove Versioning query string from your file link. Follow this steps: Open FTP and go to your EE site. Go to system > expressionengine > controllers > cp Open file Named content_files.php. On line number "370" (Line number may change) you will find $r['file_name'] ...


1

I had a situation where my web host required the use of a '?' after index.php in the .htaccess RewriteRule like this: RewriteRule ^(.*)$ /index.php?/$1 [L] And changing the values of $config['uri_protocol'] in my /system/expressionengine/config/config.php file didn't solve the problem. I finally solved it by creating a specific .htaccess rule that handled ...


1

I had a similar issue to this previously. Removing the "?" in the last RewriteRule solved the issue. Change in your .htaccess file: RewriteRule ^(.*)$ /index.php?/$1 [L] To: RewriteRule ^(.*)$ /index.php/$1 [L] Hope this helps you as much as it did me.


1

Your embed syntax is incorrect. {embed:LAST_ID} assumes that the template you're running has been embedded from within another template, and that the parent template's embed code had a parameter named LAST_ID, which has now been passed tot he template you're in. What I think you are wanting to do it use the value of an embedded template in your channel:...


1

Like @PonderTheWeb I don't see anything wrong with the code you've posted. Can you confirm that you have PHP on in the template by doing a simple: <? echo "hello world"; ?> But much more importantly: Don't trust user input! It is not good security practice to simply pass forward your $_GET variables without sanitizing them first. Fortunately ...


1

Take a look at the channel_module_create_pagination hook. Don't be fooled by the name, it doesn't just work with the channel module. I've also had success using Low Replace wrapped around pagination tags to manipulate pagination URLs. This might not be easy, though.


1

I believe it is due to %28 and %29 which stand for ( and ). You could hack EE to allow these characters but they are blocked as a precaution against code injection. utm query values look like google analytics. You probably don't care whether your campaign name as it appears in Google Analytics includes ( and ) -- so long as they are consistently reported. ...


1

In the past I've always used: # Catch any Google campaigns directed to the home page RewriteCond %{REQUEST_URI} ^/$ RewriteCond %{QUERY_STRING} ^(utm_.*) RewriteRule ^(.*)$ /index.php/ [L,PT] :)


1

Unfortunately I was unable to resolve this with SuperSearch, so ultimately I decided to migrate to Low Search instead, which was a reasonably painless process and seems to be working well.


1

Did you try with the 'paginate_base' parameter in the exp:super_search:results tag? Weirdly, I don't find any reference to this parameter in the documentation, but I'm using it in all my sites.


Only top voted, non community-wiki answers of a minimum length are eligible