Small bug - Forum Header ( * ) Link
From Another Web Company
Viewed 562 times, With a total of 15 Posts
| Have a suggestion, improvement, change or non-beta Forum Entension bug ? Please add them to the todo list
|
|
|
|
Gets Around
Wiki Edits: 4
Threads 28
Posts 161
|
|
| 12:15:17 PM - Sunday 08th, March 2009 |
|
http://usbvtrisicwww3/cxrwiki/index.php/Special:AWCforum/sf/id7/index.php?title=Restricted... Header
I click on the asteric and it doesn't bring me to the template, it just seems to refresh the page.
I was going to add this to the bug tracker, but the [add] link brings me to an errored URL.
|
|
|
|
|
|
|
|
~ What was once an opinion, became a fact, to be later proven wrong ~
|
|
|
|
|
| 8:27:55 PM - Sunday 08th, March 2009 |
|
re-pack ready
if ya have the time can you post back how it works.
|
|
|
|
|
|
Gets Around
Wiki Edits: 4
Threads 28
Posts 161
|
|
|
|
|
|
|
Gets Around
Wiki Edits: 4
Threads 28
Posts 161
|
|
| 9:02:40 PM - Sunday 08th, March 2009 |
|
Quote:Kenyu73 Mar 9th 12:53 amhttp://usbvtrisicwww3/cxrwiki/index.php/Special:AWCforum/sf/id7/index.php?title=Restricted:Forum-Interface%20Header
Still a no-go... I click the ( * ) and the screen flickers (refreshes) but doesn't open the remote template.
This works fine:
http://usbvtrisicwww3/cxrwiki/index.php/Restricted:Forum-Interface_Header
|
|
|
|
|
|
|
| 9:14:29 PM - Sunday 08th, March 2009 |
|
hummm.. somethings not right.
an you peek in the /forums/includes/gen_funk.php around line 308 and see if 'awcsf_wiki_url' is in the return ?
|
|
|
|
|
|
Gets Around
Wiki Edits: 4
Threads 28
Posts 161
|
|
| 9:21:30 PM - Sunday 08th, March 2009 |
|
[298] function add_tmpl_to_skin($tmp){
global $wgOut;
$tmplt = $tmp;
$tmplt = awc_wikipase($tmplt, $wgOut) ;
$edit = str_replace('{{', '', $tmp);
$edit = str_replace('}}', '', $edit);
return '<a href="index.php?title='.$edit.'">*</a> '. $tmplt ;
[309] }
|
|
|
|
|
|
|
| 9:31:13 PM - Sunday 08th, March 2009 |
|
something goofy must have happened cause thats not the current code.
maybe you grabbed the download before i finished updating it.
|
|
|
|
|
|
Gets Around
Wiki Edits: 4
Threads 28
Posts 161
|
|
| 9:44:42 PM - Sunday 08th, March 2009 |
|
I just downloaded the .rar again... awc_forum_beta_2.5.rar
No dice still... I checked the .rar itself and link 308 is a blank line.
|
|
|
|
|
|
|
| 10:03:24 PM - Sunday 08th, March 2009 |
|
ok, guess the download is messed up (or i forgot to upload it )
Will post back in a bit when ready.
|
|
|
|
|
|
|
| 10:27:59 PM - Sunday 08th, March 2009 |
|
| just re-upped the .rar along with a quick edit to help out with forum titles with backslashes.
|
|
|
|
|
|
Gets Around
Wiki Edits: 4
Threads 28
Posts 161
|
|
| 10:59:41 PM - Sunday 08th, March 2009 |
|
| quick question.. how do we know when we just need to copy the file and when to re-run the update?
|
|
|
|
|
|
Gets Around
Wiki Edits: 4
Threads 28
Posts 161
|
|
|
|
|
|
|
|
| 11:16:50 PM - Sunday 08th, March 2009 |
|
Being this is all in Beta, its a good idea to click the update button/link all the time, but if its really needed i've been stating that in the Beta thread.
Clicking the update button/link does the SQL table work, everything else is change when uploading the files.
In 2.5 there was a change, when a new version of the forum files are uploaded, the forum will be "locked" and there will be no choice, you will have to click the update button.
At the top of the 'awc_forum.php' file, theres a define which holds the forum files version number. This is checked/compared to the version number stored in the forums 'awc_f_config' table, if they are not the same then the forum will lock and direct the Sysops to the AdminCP update-screen.
Being this is beta and changes are happing fairly fast, to keep changing the revision number would get kind of crazy.
Do you think it would be better (or less confusing) to change the beta version now and once the beta is soild and ready for final release just change it to 3.0 ?
|
|
|
|
|
|
Gets Around
Wiki Edits: 4
Threads 28
Posts 161
|
|
| 11:26:53 PM - Sunday 08th, March 2009 |
|
Quote:AWC Mar 9th 3:08 amDo you think it would be better (or less confusing) to change the beta version now and once the beta is soild and ready for final release just change it to 3.0 ?
I think you should only set a flag to force the update only if the db needs updating and not worry about the beta version changes imo. I'd only go to 3.0 if you are introducing a huge change to the application x.y.z (x=major, y=minor, z=patch). Thats the way I always understood it...
|
|
|
|
|
|
|
| 12:17:00 AM - Monday 09th, March 2009 |
|
yea, ive never been a conventional person no matter what ive done
How it sites now, the version system seams to be working.
Any time there is an upgrade the update-script needs to be run to change the version number in the dbase. Guess time will tell how the system really works.
|
|
|
AWC's:
2.6.0 MediaWiki - Stand Alone Forum Extension Forum theme style by: AWC
|