SimpleSEF 2.0 (SMF 1.1.x and SMF 2.0)

[hartiberlin]

Hmm,
setting all values with a language variable in the database to 0
and with "de" to "en"
also did not fix it...
So how can I set the forum to english language inside the
SQL database ?

[theiceman]

got the same problem :/


smf 2 rc4 + portamx  + (german utf8)

installed over admin panel (no errors) after installtion i just get a "white" screen.

uploading the files from "2010-11-12_before_simplesef-1_1_1.tar.gz" or uploading a complete old files backup won´t help :/

whats changed in the database during the install is there some kind of changelog like for the files?

[SlammedDime]

Language really shouldn't be an issue....

You can try setting the 'integrate_pre_load' variable in the smf_settings table to an empty string and see if that helps (if there is even anything in it).

[theiceman]

yay deleting these strings helped thx

[hartiberlin]

Language really shouldn't be an issue....

You can try setting the 'integrate_pre_load' variable in the smf_settings table to an empty string and see if that helps (if there is even anything in it).

This variable had the value at my setup of:

convertQueryString,ssef_convertQueryString


Now having deleted it,
nothing happens..
I also cleared the .htaccess file...

Any other idea how to revive it ?
Still only a blank page...

Many thanks.

Regards, Stefan.

[hartiberlin]

I think I am giving up on SimpleSEF now and will not try to use it anymore.

One error source less...

I am just waiting for Feline to get her SEF fork ready to be integrated into PortaMX.
Then I will just use this and wait for this as also Google SEO
does not depends anymore so much on URL names...I guess...

Or does the other users get better Google ranking, if you have the title thema
in your URL ?

Many thanks.

Regards, Stefan.

[SlammedDime]

Language really shouldn't be an issue....

You can try setting the 'integrate_pre_load' variable in the smf_settings table to an empty string and see if that helps (if there is even anything in it).

This variable had the value at my setup of:

convertQueryString,ssef_convertQueryString


Now having deleted it,
nothing happens..
I also cleared the .htaccess file...

Any other idea how to revive it ?
Still only a blank page...

Many thanks.

Regards, Stefan.

All I could suggest then is removing anything to do with the integrate_* variables in the settings table, then if the forum becomes available, uninstall the mod, then reinstall it.

I haven't had any problems with this on my test install and I haven't been able to replicate the issue.

[kolorom]

SlammedDime if you cant post cutcode to fix 404 in v1.0.3 can you post link where i can download v1.0.3 to compare with 1.1.1 

Thanks

[truhe]

I uninstalled simplesef 1.0.3 and then installed 1.1.1.
It seems to work fine, but the Macy-Problem is back.
If I write an new pm and type a letter in the "to" textbox, the letter is replaced by "Macy" which is the member withe the id=1
this problem has been solved by a patch in 1.0.3
http://www.simplemachines.org/community/index.php?topic=352351.msg2647795;topicseen#msg2647795

(SMF 1.1.12)

Interesting, as that fix is still in place... I'll have to install 1.1.12 in a bit and test it out.

did you find time to install 1.1.12 and test it out ?

[feline]

All I could suggest then is removing anything to do with the integrate_* variables in the settings table, then if the forum becomes available, uninstall the mod, then reinstall it.

I haven't had any problems with this on my test install and I haven't been able to replicate the issue.

It's a bug in the add_integration_function (see: http://dev.simplemachines.org/mantis/view.php?id=4533)
All current (also temporary added hooks) are saved the the database ...

Fel

[SlammedDime]

I don't see how that is affecting this though... this permanently adds the hooks upon installation of the mod.

[hartiberlin]

All I could suggest then is removing anything to do with the integrate_* variables in the settings table, then if the forum becomes available, uninstall the mod, then reinstall it.

Okay, that fixed it.
I was able now to deinstall SimpleSEF after this.

It's a bug in the add_integration_function (see: http://dev.simplemachines.org/mantis/view.php?id=4533)
All current (also temporary added hooks) are saved the the database ...

Fel

Is this a major error still in the released SMF 2.0 RC4 ?
in which files must the the fixes posted there be installed ?

So any fix to this SlimmedDime ?

Could you replicate the errors ?

Many thanks.

[L'AltroWeb]

Hi! I've try this mod in my local machine (i go from prettyurls - i prefer simplesef because i can rename topic without maintain old title in url) but also if i have use reverter package (from prettyurls) old url not work - work fine if i disable simplesef.

Is there any way to migrate from prettyurls to simplesef without causing more 404?

Another question: why make url with comma (like: profile/area,forumprofile/ and wap2,/ and many others)

-

I've also removed "dot" "." from url (not util for me) and now a topic with this title: Ciao, questo è un topic di prova.

will be converted to: */ciao-questo-e-un-topic-di-prova-**.0.html instead, with prettyurls: */ciao-questo-e-un-topic-di-prova/

[SlammedDime]

There isn't a way to convert from Pretty URLs

The url uses commas to make it easier to parse

This isn't like Pretty URLs where the topic ID or board ID is not in the URL... this mod specifically puts the topic or board id in the URL to prevent any extra DB queries to find out what the actual ID is.

[L'AltroWeb]

There isn't a way to convert from Pretty URLs

This is a problem :/
I've many link in facebook and shared in many website... i can't change without a redirect (maybe i can grab old and new url from sitemap and provide manual redirect via htaccess).

The url uses commas to make it easier to parse

In my opinion isn't a good way use a comme in url. Maybe is best a simple - or _ (like from setting with standard url).

This isn't like Pretty URLs where the topic ID or board ID is not in the URL... this mod specifically puts the topic or board id in the URL to prevent any extra DB queries to find out what the actual ID is.

Yes i've understood (i've simply put an exaple without dot at the end of url - removed from settings).

[hartiberlin]

Is there soon a fix for the problems with SMF 2.0RC4 , PortaMX and AEVA 2.04 ?

Many thanks.

[Am']

Hi,

what about this bug ?

in the reading of a topic, or list of members, if you click on '...' to display to other page numbers, the link in these numbers is incorrect

when i click a number, i have this url :

http://localhost/Forum/NameBoard/NameTopic_20195.%1.html$d

any fix please ?

[SlammedDime]

I wasn't aware of any issues with AEVA and this mod... nor with PortaMX and this mod... nor with any issues on RC4 except for what is above... I wasn't able to reproduce your issue from before hartiberlin so I can't really fix something I can't reproduce.  I have altered the mod a bit so that it makes no core code changes what-so-ever to SMF (even for the admin panel and languages), so maybe that will alleviate whatever issue you were having before.

Am', I forgot about that one... I'll add it to my to-do list before the next release.

[hartiberlin]

I wasn't aware of any issues with AEVA and this mod... nor with PortaMX and this mod... nor with any issues on RC4 except for what is above... I wasn't able to reproduce your issue from before hartiberlin so I can't really fix something I can't reproduce.  I have altered the mod a bit so that it makes no core code changes what-so-ever to SMF (even for the admin panel and languages), so maybe that will alleviate whatever issue you were having before.

And where is it ?

I still see Version 1.1.1 ist still the latest, that still crashes the whole forum !

Please update immediately or send me the new version privately, so I can test it now and tell you,
if it will still crash the forum.
Many thanks.
Regards, Stefan.

[SlammedDime]

I haven't released it quite yet as I'm trying to fix Am's issue above.

Can you install a fresh copy of SMF somewhere and test the current package to see if it happens there as well?