I?m using postnuke 0.764. I did backup of database and files
Then I updated pn_bbsmile, pn_bbcose, pn_bbclick modules, I cleared all cached files etc.
During update (modules->pnForum->update) I receive an error:
Warning: Smarty error: unable to read resource: "pnforum_upgrade_27.html" in ?/Smarty.class.php on line 1095
Did any one have had this problem?
Thanks for any help.
edited by: pheski, Oct 22, 2007 - 07:48 PM
Watch
GitHub Core
Show your support for Zikula! Sign up at Github account and watch the Core project!
GitHub Modules
- internetking created topic »password problem« 25. May
- mesteele101 responded to »ERR (3): E_USER_ERROR: Smarty error: [in pagesvar:pagesitem2en line XXX]…« 25. May
- mazdev responded to »Pages 2.5.0 and updating - Page not found« 25. May
- ehdwma created topic »Hide "Register new account" and change template to 3 col« 25. May
- mesteele101 responded to »Zikula 1.3.3 - Selecting a category in Pages not working« 25. May
- mdee created topic »How to implement returnpage ?« 25. May
- nestormateo responded to »Fillters in Clip« 24. May
Zikula Blog
- Anatomy of Open Source Projects on Mar 07
- Continuous Review on Mar 01
- Not Invented Here on Feb 24
- How to Contribute Your Code at Github on Jan 13
- 10 Steps to Coding-Nirvana: Tips for Successful Module Writing on Nov 12
- Submitting Bug Report Tickets That Get Results on Aug 17
- Cozi Tricks #1: Syntax Highlighting on Aug 07
Login
pnForum 2.6 to 2.7 update
-
**unknown user**
- Rank: Registered User
- Registered: Mar 16, 2002
- Last visit: Sep 23, 2007
- Posts: 11
I know where the file is and i know that it generate error calling /includes/classes/Smarty/Smarty.class.php the problem is I can not update this module to 2.7 because of this error
-
- Rank: Expert
- Registered: Nov 23, 2003
- Last visit: Dec 13, 2009
- Posts: 1487
Check the file permissions for anything in the modules directory, if the file is there then it's likely just unable to read it.
--
Under Construction! -
**unknown user**
- Rank: Registered User
- Registered: Mar 16, 2002
- Last visit: Sep 23, 2007
- Posts: 11
-
- Rank: Softmore
- Registered: Sep 30, 2005
- Last visit: Oct 21, 2009
- Posts: 400
Sorry for being off the topic, where did you download 2.7? It's not been released officially yet, right?
edited by: Bad_Dude, Sep 23, 2007 - 07:17 PM
--
-James
My Work..... -
**unknown user**
- Rank: Registered User
- Registered: Mar 16, 2002
- Last visit: Sep 23, 2007
- Posts: 11
I think it was :)
http://noc.postnuke.…m/projects/pnforum/ -
- Rank: Expert
- Registered: Nov 23, 2003
- Last visit: Dec 13, 2009
- Posts: 1487
It definately was http://community.pos…iewpub&tid=3&pid=15.
Only samrty would throw an error on reading a Smarty resource, I assumed perms based on Smarty's inability to read the 'resource'.
--
Under Construction! -
- Rank: Expert
- Registered: Feb 27, 2005
- Last visit: Apr 18, 2010
- Posts: 1577
Same problem and I don't see the solution here.
I added the Ajax support package per instructions. I renamed the old pnForum 2.6 to zpnForum and then uploaded the pnForum 2.7 to modules and added the other pieces in their respective places.
I regenerated modules and at pnForum it now says a new version is installed but when I try to upgrade I got the error as noted above:
Code
Warning: Smarty error: unable to read resource: "pnforum_upgrade_27.html"
in
/alum1/classes/69/cm/includes/classes/Smarty/Smarty.class.php on line 1095
Interestingly, if I point my browser at pnforum_upgrade_27.html, I DO see a form but if I try to use it I get this error:
Code
The requested URL
/classes/69/cm/modules/pnForum/pntemplates/<!--[ pnmodurl modname=pnForum type=init func=
was not found on this server.
So I deleted the newly uploaded pnForum (2.7) files, renamed my old pnForum (2.6) correctly and uploaded the new (2.7) pnForum files. Then when I regenerated and attempted the upgrade I saw the interactive form but when I clicked submit, I got this error message:
Error! Called unknown function: attemptedpnForum_init_interactiveupgrade_to_2_7()
Subsequent attempts to regenerate and update give me the original Smarty line 1095 error. So I'm stuck.
Any ideas short of deleting the whole shooting match (including from the database) and then installing pnForum 2.7 fresh? (I don't mind doing this if it is the best way - no posts I need to save.)
Suggestions? (This site is living on a fairly restrictive ISP with safe_mode on - does that matter?)
Peter
edited by: pheski, Oct 22, 2007 - 08:40 AM
--
Peace
______________________________________
The commonest cause of problems is solutions. -
- Rank: Team Member
- Registered: Dec 07, 2003
- Last visit: May 09, 2010
- Posts: 2703
Hey Peter,
I would remove your renamed 2.6 from your modules directory.. I think I had a similar issue.. with a pre 2.7 release forum upgrade.. and this was part of my fixing it.. part...
--
David Pahl
Zikula Support Team -
- Rank: Expert
- Registered: Feb 27, 2005
- Last visit: Apr 18, 2010
- Posts: 1577
Thanks Dave.
Yeah, I think I screwed it up by renaming it rather than saving a copy and overwriting it - and then compounded the error by trying to do the update with the munged stuff there.
I'm at work now so I won't really have a chance to play with it until tonight, but I think the last steps I went through were to throw away the uploaded 2.7, rename the 2.6 back to pnForum, then upload the 2.7 overwriting the 2.6 pnForum and then trying the upgrade. That's when I got further and actually saw the 'interactive upgrade page' but when I tried to submit from 2.6 to 2.7 (the only option it gave me) I got the second error:
attemptedpnForum_init_interactiveupgrade_to_2_7()
When I get home I will check to be sure that the function is actually there. And perhaps I will remove all the pnForum files, not change the database, upload the pnForum 2.6 distribution and then overwrite that with the pnForum 2/7 distribution and see if that helps.
If not, I guess I just purge the whole thing and start fresh...
I have had some trouble on this server before because of the safe_mode thing. On occasion scripts won't run because the server owns the file and I own the script.
Peter
edited by: pheski, Oct 22, 2007 - 11:12 AM
--
Peace
______________________________________
The commonest cause of problems is solutions. -
- Rank: Expert
- Registered: Nov 23, 2003
- Last visit: Dec 13, 2009
- Posts: 1487
I've done this before with my own module... the trick of it is pninit.php gets loaded for every module upon regenerate so you end up with duplicates in the module table, hence pnInternalConfusion. Renaming the modules pninit.php might fix this as well.
--
Under Construction! -
- Rank: Expert
- Registered: Feb 27, 2005
- Last visit: Apr 18, 2010
- Posts: 1577
Topiatic
..the trick of it is pninit.php gets loaded for every module upon regenerate so you end up with duplicates in the module table, hence pnInternalConfusion. Renaming the modules pninit.php might fix this as well.
You nailed it Topiatic - and thanks. I checked the tables and I had an entry for each of my renamed pnForum versions (2 extras). I eliminated those, trashed the pnForum files in /modules, reuploaded pnForum 2.6, regenerated modules and it asked me to upgrade and activate which I did and now 2.6 worked. Then I simply uploaded 2.7 and overwrote 2.6, regenerated modules, and then the upgrade process worked flawlessly.
I then tried several variations here in my sandbox, and it does appear that it is essential to upgrade by simply overwriting 2.6 with 2.7. As soon as you leave a pninit.php there and regenerate, you are asking for trouble: you get an entry in the modules table for every version. Renaming that file (stripping the PHP from the end) prevents the problem.
I *thought* I had done some upgrades in the past using the rename method - but perhaps that was theme work, not module work.
At any rate, it would be worth adding a line about this in the pnForum docs. I'll look later in the Wiki to see if I can find a place for this. It is probably a general principle and should be under modules in the Wiki.
Peter
edited by: pheski, Oct 22, 2007 - 07:50 PM
--
Peace
______________________________________
The commonest cause of problems is solutions.
- Moderated by:
- Support
