1. Both buyer and seller are verified.
2. Buyer is logged in to ExpressionEngine when purchasing.
3. The email address in the Simple Commerce module matches that entered into PayPal. This is case sensitive.
]]>
MySQL Error:
MySQL ERROR:
Error Number: 1117
Description: Too many columns
or:
#1030 - Got error 139 from storage engine
If you encounter these symptoms, it is best to remove custom fields until the symptom is gone.
In most cases where this many custom fields are used, there are better approaches to storing the data. If you need assistance in discovering an approach that will work for your site, please post on the forums.
There is no work-around for this MySQL limitation at this time.
For more information, please review this thread.
]]>First, create your MetaWeblog API configuration, and take note of the id of the weblog you have setup this configuration for. In this example, we’ll assume the weblog id is 4. Copy the endpoint URL provided in the MetaWeblog API control panel to the clipboard.
http://example.com/index.php?ACT=47&id=1
Next, create your RSD XML file. You can use an ExpressionEngine template to do this (choose “XML” for the template type), and use the following format as a guide. In this example, we’re naming the template ‘rsd.xml’ and placing it in the ‘site’ template group. The link you copied in the first step goes in the apiLink attribute, and the weblog id goes in the blogID attribute.
<?xml version="1.0" ?>
<rsd version="1.0" xmlns="http://archipelago.phrasewise.com/rsd" >
<service>
<engineName>ExpressionEngine</engineName>
<engineLink>http://expressionengine.com/</engineLink>
<homePageLink>http://example.com/</homePageLink>
<apis>
<api name="MetaWeblog" preferred="true" apiLink="http://example.com/index.php?ACT=47&id=1" blogID="4" />
</apis>
</service>
</rsd>
Note that this will also work with the Blogger API. The same <api> tag would be used, but the name attribute would use Blogger. You can add additional <api> tags for other MetaWeblog endpoint URLs and weblogs, but only one should have preferred set to true. The others should set this value to false.
The last step is to put an auto-discovery link in the <head> section of your HTML. Normally this would be in every page, much like your stylesheets and feed links.
<link rel="EditURI" type="application/rsd+xml" title="RSD" href="{path='site/rsd.xml'}" />
And that’s it! Now when using applications and services that utilize the MetaWeblog API, instead of typing in the full endpoint URL, you can simply give it your domain name, and the application or service will do the legwork for you.
]]>As this has security implications, we recommend you disable this behavior inside any folders you allow file uploads via ExpressionEngine if you are running Apache. The following .htaccess file will generally work.
1) Create a file called “.htaccess” (exactly like that, no additional file extensions).
2) Place the following into its contents.
# Protects from Apache reading double suffixes
SetHandler EE_Upload_Security_Do_Not_Remove
3) Upload this file into the each upload folder within your ExpressionEngine installation, or if your upload folders are all contained inside a common parent folder, you can place one copy of it there.
Notes:
- We always recommend you work with your webhost when working with server configuration.
- If you already have an .htaccess file in your installation, simply add the “SetHandler” line to it.
- Some users have trouble with this file name, and you may want to create “htaccess.txt” and rename it after you’ve uploaded it to your webserver.
]]>Answer: This problem is caused by a changed setting in your config.php file:
$conf['cp_url'] = "http://secondsite.com/admin.php";
instead of
$conf['cp_url'] = "http://mainsite.com/system/";
You can edit your config.php to put back the original setting, or you can add that setting to your individual site’s path.php file.
Example:
$system_path = "./system/";
$cp_url = 'http://www.mainsite.com/admin.php';
(You can also copy the admin.php file from the /system/utilities folder into the root of your ExpressionEngine install.)
NOTE: Before editing your config.php and/or path.php files(s), back them up first.
In order for this fix to work, you may need to clear your site wide cookies. Information on how to do this will be in your browser’s documentation.
]]>
cPanel subdomains are a bit different then standard subdomains done via htaccess. Here are the steps to make a forum work as a subdomain with cPanel.
1) Go into cPanel, and “Create a Subdomain”. Set it to forum.yourdomain.com. cPanel will want to create a directory for you at home/public_html/forum. This is a good thing.
2) FTP into this newly created directory, and follow the directions for Running Multiple Domains or Subdomains or Subsites the “classic” way.
3) You should now have identical sites at http://www.yoursite.com and forum.yoursite.com. The trick now is to point all the subdomain requests to http://www.yoursite.com/index.php/forum. There are many techniques you could use for URL rewriting, but here’s a simple .htaccess file that will move all requests
RewriteEngine on
RewriteCond $1 !^(index\.php) [NC]
RewriteRule ^(.*)$ /index.php/forum/$1 [L]
This most often happens when mis-setting the cookie value and leaving off the leading period. You can add this line into /system/config.php to change it:
$conf['cookie_domain'] = "";
This should allow you to enter the control panel. You will want to head to the appropriate setting and submit it in the control panel to force the update to the database. Once that is done, remove the over-ride from config.php.
]]>
Of course, you are free to use a Commercial licensed Site for personal and non-profit use, but you are not allowed to run commercial/for-profit websites from a Personal License.
]]>Instructions for updating Mark Huot’s Pages module to the newer version (now named “Tome”) can be found here: http://docs.markhuot.com/ee/modules/tome/
Note to Developers: This scenario demonstrates the importance of giving unique class and table names to your add-ons, and avoiding unchecked file dependencies. The suggested naming convention is to use identifying prefixes for all class, file, and table names. In so doing, you will avoid potential collisions with ExpressionEngine native classes, conflicts with other third party developers’ add-ons, and even potential conflicts with non-ExpressionEngine based PHP scripts that users may be running on their sites.
]]>
{exp:magpie url="http://user:password@example.com/news.xml" limit="10" refresh="720"}
<ul>
{items}
<li><a href="{link}">{title}</a></li>
{/items}
</ul>
{/exp:magpie}
Warning: If you do this, anyone with access to edit that template will be able to view your login information for that feed, so use this trick with extreme caution.
]]>See this feature request where Paul explains that the best way to have high-ascii case insensitive searches is through your MySQL settings. On MySQL versions 4.1 and above, setting your collation to match your language should resolve the issue.
It’s also possible for searches to be case sensitive if your MySQL collation setting is one that is by nature case insensitive, such as utf8_bin.
]]>