SMF 2.0 Release Candidate 2 is out for Charter Members!

[SoLoGHoST]

How come Arantor?  If I do in package-info.xml installs for both RC1.2 and RC2 like so...

Install for RC1-1, RC1.2

Code Select Expand

<install for="2.0 - 2.0.99">

Install for RC2

Code Select Expand

<install for="2.0 RC2">

And do the same for uninstall and upgrade.  This does it for both versions and create separate .xml files for each and separate database install files for each.  This works just fine.

[Arantor]

Assuming you want to distribute it on the mod site, you either need to delete the file already there, or at least replace it with your newly checked package?

[SoLoGHoST]

Ofcourse, I'll just replace it with my newly checked package, which supports both RC1.2 and RC2.  However, still not sure about replacing it just yet on the mod site since there may be some changes in RC2 before it goes public that may need to be addressed within my PM Attachments mod, so we'll see.

[Arantor]

You can have both together if they're different names, by the way, then remove the preliminary RC2 version later.

[SoLoGHoST]

Yeah, exactly, better safe than sorry.

[*Can]

Is Queryless urls? Do you have a demo?

[Arantor]

Queryless URLs have been around since 1.1. Basically it means removing the ? from the URL.

Basically instead of this thread being http://www.simplemachines.org/community/index.php?topic=340177.0 it would become http://www.simplemachines.org/community/index.php/topic,340177.0.html

Board links go from http://www.simplemachines.org/community/index.php?board=1.0 to http://www.simplemachines.org/community/index.php/board,1.0.html

Not really necessary for modern search engines.

[*Can]

Queryless URLs have been around since 1.1. Basically it means removing the ? from the URL.

Basically instead of this thread being http://www.simplemachines.org/community/index.php?topic=340177.0 it would become http://www.simplemachines.org/community/index.php/topic,340177.0.html

Board links go from http://www.simplemachines.org/community/index.php?board=1.0 to http://www.simplemachines.org/community/index.php/board,1.0.html

Not really necessary for modern search engines.

Thank you I know. But inadequate. Why not be as pretty urls?

[Arantor]

Because queryless URLs works on more servers than Pretty URLs, plus Pretty URLs adds a performance hit queryless URLs don't. And Google (and other search engines) have said there is little/no SEO benefit to doing it anyway.

Additionally, in a typical forum, topic names usually aren't entirely helpful anyway.

[Nao 尚]

PrettyURLs is mostly helpful when your topics act like blog posts. In which case it's a really, really nice addition.

[*Can]

Because queryless URLs works on more servers than Pretty URLs, plus Pretty URLs adds a performance hit queryless URLs don't. And Google (and other search engines) have said there is little/no SEO benefit to doing it anyway.

Additionally, in a typical forum, topic names usually aren't entirely helpful anyway.

SMF automated SEO needs! postname.html more appropriate.
example vbSEO > http://www.vbseo.com

PrettyURLs is mostly helpful when your topics act like blog posts. In which case it's a really, really nice addition.

[Arantor]

It only really makes memorable URLs, still doesn't have much/any SEO benefit.

Google has specifically advised AGAINST rewriting URLs anyway.

[Kenny01]

Because queryless URLs works on more servers than Pretty URLs, plus Pretty URLs adds a performance hit queryless URLs don't. And Google (and other search engines) have said there is little/no SEO benefit to doing it anyway.

Additionally, in a typical forum, topic names usually aren't entirely helpful anyway.

SMF automated SEO needs! postname.html more appropriate.
example vbSEO > http://www.vbseo.com

PrettyURLs is mostly helpful when your topics act like blog posts. In which case it's a really, really nice addition.

Stuffs like this will never help your site, what you need for traffic, is simply regular contents, more contents = more traffic.

[*Can]

It only really makes memorable URLs, still doesn't have much/any SEO benefit.

Google has specifically advised AGAINST rewriting URLs anyway.

Okey. But you said I prefer seo.  But you said We prefer postname.html seo

SMF, 2 different versions is ridiculous. 1.1.x will be completed when. ( Require 1.1.x termination )

Because queryless URLs works on more servers than Pretty URLs, plus Pretty URLs adds a performance hit queryless URLs don't. And Google (and other search engines) have said there is little/no SEO benefit to doing it anyway.

Additionally, in a typical forum, topic names usually aren't entirely helpful anyway.

SMF automated SEO needs! postname.html more appropriate.
example vbSEO > http://www.vbseo.com

PrettyURLs is mostly helpful when your topics act like blog posts. In which case it's a really, really nice addition.

Stuffs like this will never help your site, what you need for traffic, is simply regular contents, more contents = more traffic.

I think the content is not important. SEO = Hit = Money

[IchBin™]

I think the content is not important. SEO = Hit = Money

If you read around the inter-webs you'll see that this has been proven false many, many times.

[Kenny01]

Your contents must contain keywords related to your site in both titles and header.

[Nao 尚]

I think the content is not important. SEO = Hit = Money

W-O-W.
Message of the month.

[Kenny01]

I think the content is not important. SEO = Hit = Money

W-O-W.
Message of the month.

Really funny, i'm yet to see a site without contents.

[Arantor]

SMF, 2 different versions is ridiculous. 1.1.x will be completed when. ( Require 1.1.x termination )

1.1 went gold 3 years ago. 2.0 is the development version and when 2.0 is completed (rather than in final betas) it will replace 1.1 as the main version. In many cases, 1.1 is already considered obsolete and is not maintained except for security.

But content is the KEY for SEO. Every guide every written on SEO requires content, how can you optimise for search engines if you have nothing to optimise for?

[Kenny01]

true talk Arantor.