Permalinks

By default, Osclass uses URLs with query strings (“?id=123”) that are less readable and less SEO-friendly. Enabling Permalinks lets you replace those with descriptive URLs (e.g., /cars/honda-civic-i123). Doing so can significantly improve your site’s SEO, usability, and future compatibility.

Important: Misconfiguration can break your site or cause overlapping routes. Always ensure each page type has a unique pattern and that your server supports rewrite rules (e.g., Apache mod_rewrite).

Enabling Friendly URLs

• Enable Friendly URLs: Check the box to activate permalinks. This typically requires a working .htaccess (on Apache servers) or alternative configuration (for Nginx, Lighttpd, etc.).
• Osclass will generate additional fields once permalinks are enabled, letting you define URL patterns.

Core Pages Structure

• Listing URL: The pattern that single item pages follow, e.g. {CATEGORIES}/{ITEM_TITLE}-i{ITEM_ID}.
  Required placeholder: {ITEM_ID}
  Accepted placeholders: {CATEGORIES}, {CATEGORY}, {ITEM_TITLE}, {ITEM_COUNTRY}, {ITEM_COUNTRY_CODE}, {ITEM_REGION}, {ITEM_CITY}, {ITEM_CITY_AREA}, {ITEM_ZIP}, {ITEM_CONTACT_NAME}, {ITEM_CONTACT_EMAIL}, {ITEM_CURRENCY_CODE}, {ITEM_PUB_DATE}.
  Make sure each URL is unique by including {ITEM_ID} or something that differentiates items.
• Static Page URL: For pages you create under “Pages” in the backoffice.
  Accepted placeholders: {PAGE_ID}, {PAGE_SLUG}.
  If you do not include {PAGE_ID}, be sure to add a prefix (e.g., help/{PAGE_SLUG}) so that URLs don’t conflict with other routes.
• Category Page URL: Determines the link structure for category listings, e.g. {CATEGORIES}.
  Accepted placeholders: {CATEGORY_ID}, {CATEGORY_NAME}, {CATEGORIES}.

Search Page Structure

• Search Prefix URL: A small static string included before region, city, or category paths, such as search or listings.
• Search URL: Base string for the search route, e.g. search.
• Search Keyword Country / Region / City / City Area / Category / User / Pattern: These are sub-path keywords for filtering searches by those parameters. For instance, country might appear in /search/country/spain.
• Search Order & Order Type: Controls query parameters for sorting results by date, price, relevance, etc.
• Search Price Min/Max, Search With Picture, Search Premium Only, Search With Phone, Search Show As, Search Page Number: Adjust how these additional filters appear in the URL.

Custom Search Page Structure (Optional)

• Enable Custom Search Rules: If checked, you can define specific patterns (e.g., {sRegion}/{sCity}/{sPattern}) that override the default search URLs when a matching set of parameters is detected.
• Strict Form: When enabled, only queries that match the rule’s parameters exactly (no additional parameters) will use that rule. Otherwise, extra search parameters can appear in the final URL.
• Rule Priority: Each rule is labeled A through Z. A is the lowest priority, Z the highest. Osclass applies the first matching rule from Z down to A.
• Ignored Parameters: Some parameters like lang, iPage, sShowAs, sOrder, iOrderType are appended at the end and are not part of custom matching.

Additional Notes on Custom Search Rules

• You can define multiple rules for different combinations of search parameters. For example, {sCategory}/{sCity}/{sPattern} could apply to searches containing both a category and city parameter plus a keyword pattern.
• Each rule is labeled from A to Z. If multiple rules match, Osclass applies the highest priority (closest to Z) first.
• When strict form is enabled, all of the parameters required by the rule must appear (and no extra ones) for the rule to match. If a user adds additional filters outside those specified, the rule will be ignored.
• If a rule does not strictly match or if it’s left empty, Osclass tries lower-priority rules or defaults back to the canonical search URL structure.
• Custom rules override the standard (canonical) URL paths, so carefully test your most generic rules before adding highly specific ones to avoid conflicts.
• When a custom rule is activated, unrecognized parameters (like lang or iPage) will still be appended to the final URL, ensuring all search filters remain in effect.
• You may use any valid search parameter name in your rules, such as sPriceMin, bPic, or bPremium. Review your theme or plugin documentation to confirm parameter names.

Read more about Custom Search Rules.

Listing Pages Structure

• item/mark, item/send-friend, item/contact, item/new, etc. These define the sub-URL for each listing-related action, such as “mark item as spam,” “send to friend,” or “edit.”
• Use short, descriptive names (e.g., item/contact) to keep your URLs clean and intuitive.

User Pages Structure

• user/login, user/register, user/dashboard, etc. Sets how user-related actions are represented in permalinks.
• If you rename user/login to signin, for example, the login URL becomes https://example.com/signin when using friendly URLs.

Other Pages Structure

• contact: Path to your site’s contact form page.
• feed: RSS or Atom feed address (if enabled).
• language: Switching between multiple languages (if applicable).

.htaccess Configuration

• If Apache mod_rewrite is enabled, Osclass needs an .htaccess file in your site’s root folder. Its contents must redirect all non-file, non-directory requests back to index.php for permalinks to function.
• A minimal recommended .htaccess often looks like:

  <IfModule mod_rewrite.c>
  RewriteEngine On
  RewriteBase /
  RewriteRule ^index\.php$ - [L]
  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteCond %{REQUEST_FILENAME} !-d
  RewriteRule . /index.php [L]
  </IfModule>

  Make sure RewriteBase matches your site’s subdirectory if applicable (e.g. /classifieds/).
• If you see a warning that .htaccess could not be found, create one and verify file permissions or consult your hosting provider for assistance.

After finalizing the rules, click Save changes and test your site thoroughly. Confirm that listings, categories, search pages, and user-related pages all resolve to the correct URLs. If URLs return 404 or unexpected results, revert or adjust your settings to fix any conflicts.

Additional Details & Advanced Tips

The following extra considerations can help you avoid common pitfalls and maximize the benefits of friendly URLs:

• Handling Overlapping Routes: Always ensure that no two URL structures generate identical paths. For instance, if you remove {ITEM_ID} from your “Listing URL” pattern, then your site might conflict with similarly named static pages or categories. The required placeholder ({ITEM_ID}) is the simplest way to guarantee uniqueness.
• Subdomain Usage: Some advanced setups place regions or languages in a subdomain (e.g., en.example.com or newyork.example.com). Osclass offers partial support for subdomains, but you must ensure your DNS and web server configuration properly map subdomains to the main Osclass installation. If you choose this route, additional rewrite rules beyond the standard .htaccess may be required.
• Parameter-Based Canonical URLs: When using both custom rules and canonical (default) structures, be mindful that search engines need a single canonical version to avoid duplicate indexing. Osclass tries to assign canonical paths automatically, but any missing or conflicting placeholders can disrupt it.
• Cache Considerations: If you have a caching system (plugin or server-level), clear or refresh it after changing permalinks. Otherwise, previously cached URLs might break or return stale data.
• Local Hosting vs. Live Hosting: If you’re testing on a local Apache environment (like XAMPP or WAMP), confirm that mod_rewrite is enabled. Upon moving to a production server, you may need to adjust the RewriteBase directive if your site is in a subdirectory.
• Troubleshooting Common Errors:
  • 404 Not Found or Internal Server Error (500): Usually indicates a missing or incorrect .htaccess, or conflicting custom rules within your permalinks configuration.
  • Infinite Redirect: Check if RewriteBase or your custom rule set is causing a loop. Sometimes, rewriting from one path to an identical one triggers endless redirects.
  • “Too Many Redirects”: Often happens if multiple rewrite systems conflict (e.g., a WordPress .htaccess alongside Osclass, or mismatched custom subdomain rules). Keep your rewrite logic consolidated and consistent.

By following these guidelines and verifying your site’s URL patterns do not overlap, you can enjoy the SEO and user experience benefits of permalinks without risking broken links or duplicate content. Good testing and backups before big URL changes are always recommended.