Hi!
Quote:
I will not leave the others without help, but you may restrain any help from me for yourself.
Please don't take the following to seriously, I'm just trying to make a point here...
Great! Good job. That's a community spirit. Is lifetype working for everyone else aside of sailjapan and me? or is someone elso already working on the fix on it? Because if so than WTF am I wasting my time on?
But now seriously. I have not been working on anything web related for around 3 years and even before that I was just learning php, so I don't think it is reasonable on your side to witheld information that might prove useful, don't you think?
Ghia, I didn't mean to offend you in any way by what I wrote in previous or this post and I know you did not mean to either, I think it's down to lack of sleep and my overall nervousness, so I will think of it as a misunderstanding on both sides or at least on mine and I will not take up on that anymore.
Quote:
Yes, XOOPS has a Frameworks directory, but they have in no way the complete Frameworks. If you had followed the readme instructions and downloaded the Frameworks of the link, you could have seen it for yourself that important directories where missing.
Yeah, of course I could have if only I had your knowledge on xoops. BUT I DO NOT!!! The last time I was using XOOPS (read above) it was when frameworks were introduced or started beeing widely used by some modules. I came back after a long break I dload new release and try to make something out of it.Bbasics did not change, but coding did, XOOPS has changed a lot as well, things were moved about, added, removed or incorporated into core. I did see that frameworks in 2.3.1 is somewhat empty, but try to put yourself in my position and take a look at its readme.txt:
XOOPS Frameworks
For common frameworks shared by XOOPS modules.
A framework could be adopted into XOOPS core once it is proven.
The structure: {XOOPS_ROOT_PATH}/Frameworks/myframework/xoopsmyframework.php
Content of myframework.php:
<?php
class XoopsMyframework
{
function __construct()
{
}
... } ?>
Very informative for a new user or a person who comes back like me, isn't it?
Than an all important part of frameworks/art changelog:
"1 Cleaned for XOOPS 2.3.0 (phppp)"
and xoops_version for art
" * @version $Id: xoops_version.php 1901 2008-07-26 04:05:57Z phppp $"
It is dated 4 months ago.
I assumed, by reading above that other stuff got incorporated (and some of it did in one way or another).
So don't you think that insisting on if I've read I would know is a bit pointless? I did read it and I have seen the requirements.
I think we should stop talking about what I could have or should have done and concentrate on what I/we could or should do. And please, I do need your help Ghia, so if or when you know something please contibute. I appreciate your input.
Now, getting down to what I came here for.
Lifetype is very temperamental and even though I know what it needs in frameworks. I does not install the proper way (returns a blank screen), but it does create tables and everything.
Folder needed from original frameworks is captcha
calls come from:
class/data/validator/captchavalidator.class.php and
class/view/viewarticleview.class.php
for
Frameworks/captcha/captcha.php
and
Frameworks/captcha/formcaptcha.php respectively
Surprisingly, you may find them in XOOPS class folder (captcha and xoopsform) as well. Their code differ however what renders them useless (at least I think it does).
There are 4 other calls to Frameworks in other files, but they call on art and textsanitizer which are included in the XOOPS native frameworks.
I've copied the captcha folder and after 15 minutes of fiddling had my lifetype working. As I've said it is a temperamental module and I had a problem with blogcreation (was getting a message about not being attached to any blogs or something)
Problems still occuring:
-blank page after install
-when clicking on the lifetype likn in main menu user is redirected to the first blog meaning in my case admins blog
-userlist in lifetype is blank (didn't check prefs yet, it may be so intentionally)
Other issues:
-No way to go back to your site other than clicking on register. link needs to be added in the main template.
-once in someones blog there is no way to go back to summary page
I think that's it from me for now.
Take care.
