Best of joomla gives you news, joomla templates, tutorials and websites about Joomla , FireBoard and FireMessage official page.
| No account yet?   |
Welcome, Guest
Please Login or Register.    Lost Password?
Re:Problems after upgrading from 1.0.3 to 1.0.4 (1 viewing) (1) Guest
Go to bottom Favoured: 0
TOPIC: Re:Problems after upgrading from 1.0.3 to 1.0.4
#44039
Problems after upgrading from 1.0.3 to 1.0.4 6 Months, 2 Weeks ago  
Today I downloaded the updated 1.0.4 version (the patch files) and installed it according to the documentation.

I have two problems:

1. In the Administration mode I always see the Database Wizard which asks me to complete the installation (either a Clean Installation or an Upgrade from Joomlaboard). No matter what I select the Database Wizard doesn't go away.

2. In the Administration mode the page buttons (goto page 1,2 next page, end,...) don't work. If I click on them then nothing happens.
Firebug reports the following error:
document.adminForm.limitstart has no properties
onclick(click clientX=0, clientY=0)


Any ideas?

Regards,
Stephan
schoenbi (User)
Fresh Boarder
Posts: 6
graphgraph
User Offline Click here to see the profile of this user
Logged Logged
 
The administrator has disabled public write access.  
#44885
Re:Problems after upgrading from 1.0.3 to 1.0.4 6 Months, 1 Week ago  
I'm not having your first problem.

Sounds like Fireboard doesn't have the right username/password/database name?

I am having your second problem.

Joomla 1.5.1
Fireboard 1.4 (patched)
Community Builder 1.1

Marty
moleski (User)
Fresh Boarder
Posts: 8
graphgraph
User Offline Click here to see the profile of this user
Logged Logged
 
The administrator has disabled public write access.  
#44887
Re:Problems after upgrading from 1.0.3 to 1.0.4 6 Months, 1 Week ago  
Do not use the patch files. Uninstall and reinstall using the FULL package. I cannot say this will work, especially with 1.5 (FireBoard is NOT really compatible with 1.5 even in legacy mode) but I can say there are issues with the patch files NO ONE has been able to solve. Please check the first 2 topics in this category.
grumblemarc (User)
Platinum Boarder
Posts: 3557
graph
User Offline Click here to see the profile of this user
Gender: Male
Logged Logged
 
The administrator has disabled public write access.  
#44912
Re:Problems after upgrading from 1.0.3 to 1.0.4 6 Months, 1 Week ago  
Thank you, I will try to uninstall and reinstall the full package then.

Stephan
schoenbi (User)
Fresh Boarder
Posts: 6
graphgraph
User Offline Click here to see the profile of this user
Logged Logged
 
The administrator has disabled public write access.  
#44946
Re:Problems after upgrading from 1.0.3 to 1.0.4 6 Months, 1 Week ago  
I also have this problem with pagination, but have done a fresh install of 1.04
vickyh (User)
Fresh Boarder
Posts: 6
graphgraph
User Offline Click here to see the profile of this user
Logged Logged
 
Last Edit: 2008/02/22 19:50 By vickyh. Reason: better explanation
 
The administrator has disabled public write access.  
#44957
Re:Problems after upgrading from 1.0.3 to 1.0.4 6 Months, 1 Week ago  
Looks to me as though the pagination problem is from Joomla not making limistart a variable in the adminForm. It's not CB's fault.

I haven't been able to track down where the error is in the Joomla libraries. I think it's in a model somewhere (this morning's theory).

Marty
moleski (User)
Fresh Boarder
Posts: 8
graphgraph
User Offline Click here to see the profile of this user
Logged Logged
 
The administrator has disabled public write access.  
#44979
Re:Problems after upgrading from 1.0.3 to 1.0.4 6 Months, 1 Week ago  
I've fixed the problem with the page links and the page navigation buttons.

Problem: clicking on any of the pagenav stuff gives a js error message that document.adminform.liststart has no properties.

Reason: liststart is not defined anywhere in the form.

Cure: put in the html when the adminForm is created.

../administrator/components/com_fireboard|admin.fireboard.html.php

I just threw the definition of liststart into all the instances where a name = "adminForm" is found.

In fact, this seems to be the function that needed the cure:

Code:

function showProfiles($option, $mosConfig_lang, &$profileList, $countPL, $pageNavSP, $order, $search)
    {
...

        

... = some php stuff snipped so that the FB parser doesn't cut the rest of the code out ...
        
   



I don't see any reason not to let the other ones ride for the time being.
moleski (User)
Fresh Boarder
Posts: 8
graphgraph
User Offline Click here to see the profile of this user
Logged Logged
 
Last Edit: 2008/02/22 23:13 By moleski.
 
The administrator has disabled public write access.  
#50049
Re:Problems after upgrading from 1.0.3 to 1.0.4 3 Months, 3 Weeks ago  
moleski wrote:
I've fixed the problem with the page links and the page navigation buttons.

Problem: clicking on any of the pagenav stuff gives a js error message that document.adminform.liststart has no properties.

Reason: liststart is not defined anywhere in the form.

Cure: put in the html when the adminForm is created.

../administrator/components/com_fireboard/dmin.fireboard.html.php

I just threw the definition of liststart into all the instances where a name = "adminForm" is found.


It seems to be a general pagination issue when the Legacy is on (J! 1.5.x)

Anyway, could you please tell me what html line and where exactly I should put it, when the adminForm is created in the file?
I can see the lines with adminForm, in that file, but I dont understand what to do exactly.

Thank for helping
Dukessa (User)
Fresh Boarder
Posts: 5
graphgraph
User Offline Click here to see the profile of this user
Logged Logged
 
The administrator has disabled public write access.  
Go to top
Powered by FireBoard - Creditsget the latest posts directly to your desktop