msg# 1
I to install with xoops2.0.16 and Pico 1.17 and I can't figure out how or where to add any content.
Contents list | Permissions of Categories | Import/Sync | Preferences |
ONly "Preferences" is working the others page blank??
---> I to modify class/smarty/xoops_plugins/resource.db.php with the guide:
http://xoops.peak.ne.jp/md/news/index.php?page=article&storyid=354and continue obtaining page blank.
Help for that it works in xoops2.0.16
Votes:37
Average:8.38
msg# 1.1
I had the same problem even after making the smarty modification.
What I found was that if I accessed the Content List, Permissions, etc. from the popup menu when I placed my mouse on the module Icon, I could access the content. But if I tried to use the tabs across the screen, I would just get a blank page. So that was how I added my original test content. Then suddenly, at some later date, the tabs began working. It may have been after I got my first category created.
So you might try selecting the options from the popup menu rather than the tabs and see if that works.
Votes:8
Average:7.50
msg# 1.1.1
In my environment, pico works perfectly with 2.0.16 from xoops.org.
At first, turn debug ON.
If you see any errors report it.
Else, It must be the problem of the template's compatibility of 2.0.14/15/16 (I say BUG).
I show three ways to fix that for you.
- Correcting Patched file
Try to download and replace it.
http://www.peak.ne.jp/support/xoops/xoops-2.0.16-resource.db.fixed.zip(Best way)
- Using custom templates set
Install altsys
Copy the template of pico to new template set in altsys
Set the template set as default in your preferences
(Second way)
- Copy the template files into public side
(The worst way)
Anyway, you should install altsys for solving template problems also.
Votes:6
Average:8.33
msg# 1.1.1.1
width debug on:
Notice: Only variables should be assigned by reference in file /xoops_trust_path/modules/pico/admin/contents.php line 19
Notice: Constant _MI_formulize_NOTIFY_FORM already defined in file /modules/formulize/language/english/modinfo.php line 16
Notice: Use of undefined constant _MI_formulize_NOTIFY_FORM_DESC - assumed '_MI_formulize_NOTIFY_FORM_DESC' in file /modules/formulize/xoops_version.php line 164
Warning: filemtime() [function.filemtime]: Stat failed for /modules/congresos/templates/congresos_admin_contents.html (errno=2 - No such file or directory) in file /class/smarty/xoops_plugins/resource.db.php line 32
Mi pico install in a directory "congresos"
Votes:4
Average:7.50
msg# 1.1.1.1.1
- confirm resource.db.php is fixed correctly
- remove all files under templates_c/
- update the module
Votes:6
Average:6.67
msg# 1.1.1.1.1.1
I'm using Pico 1.2 with XOOPS 2.0.16. I'm getting the same problem as was originally decsribed (preferences pages shows up but nothing else). I turned on debug and received the following error on the Content List and Import/Sync pages:
Notice: Constant _DB_POSLINE_DESC already defined in file /modules/backup/language/english/modinfo.php line 24
The other two tabs did not make errors.
EDIT: I have already made the resource.db.php change that was suggested above as the "best way" to fix the error. The tabs did not work before or after that fix was applied.
Votes:5
Average:2.00
msg# 1.1.1.1.1.1.1
Quote:
mdeming wrotes:
I'm using Pico 1.2 with XOOPS 2.0.16. I'm getting the same problem as was originally decsribed (preferences pages shows up but nothing else). I turned on debug and received the following error on the Content List and Import/Sync pages:
Notice: Constant _DB_POSLINE_DESC already defined in file /modules/backup/language/english/modinfo.php line 24
I cannot understand why such an error is displayed.
Have you patched into system by the module named "backup"?
Quote:
EDIT: I have already made the resource.db.php change that was suggested above as the "best way" to fix the error. The tabs did not work before or after that fix was applied.
Have you cleared templates_c/* ?
Votes:5
Average:2.00
msg# 1.1.1.1.1.1.1.1
Quote:
GIJOE wrotes:
Have you cleared templates_c/* ?
Aha! I forgot to perform that step. Thank you very much for your help.
Votes:0
Average:0.00
msg# 1.2
I had this same problem with Pico 1.2. I found I could fix it by going to admin => system => templates and manually generating the templates for this module (because it didn't seem to do it automatically).
Then it worked fine. Great module :)
Votes:0
Average:0.00
msg# 1.2.1
hi crushdepth.
Quote:
I had this same problem with Pico 1.2. I found I could fix it by going to admin => system => templates and manually generating the templates for this module (because it didn't seem to do it automatically).
I don't recommend to clone all templates via "admin => system => templates".
It makes management of templates too complex.
I recommend to clone templates at minimum via altsys.
Votes:1
Average:10.00