Ok I have done everything what is human possible to erase every error on my side or on the server side.


It is either a module issue.

or it is different version of 2.4.4 on sourceforge


and with my example of fantastico installer with justhost.


I have now 4 installations of xoops 2.4.4 manual install of
2.4.4 with files from sourceforge

(the hosting company I would say professionals unzipped the file
on the server, so definitely no file is missing )


2 installations per autoinstaller where the module works but the
admin/index.php loads quite slow in comparison to other modules.

but last not least it loads


My last try would be if someone provides me with the 2.4.4 which is on justhost.com Fantastico to try this version.


but you should be the experts and tell me if this makes any sense , with this kind of error message it should be rather
a module issue because all other modules I can open the
admin/index.php

So something is wrong.

Again the message - and again the file is faultless like one of my predecessor already checked that.


Parse error: syntax error, unexpected $end in

/business/modules/yellow-pages/admin/index.php on line 1730


but there is no syntax error



a real headache

not sure but I think you did not get the problem message which is

Parse error: syntax error, unexpected $end in /usr/www/users/sharon13/mydomain/folder/modules/yellow-pages/admin/index.php on line 1730

so of course I did what you suggested but it is not a matter of the cache I believe.

And there was some guy with the same issue.

the problem is still existing and it is either module related or like I mentioned before that there are different versions of cor on
sourcefourge and with the auto installers of hosting companies.

Well I really would like to get the zip file which is with the hosting companies who use Fantastico or other autoinstallers.

because with this version the module works for whatever reason.


I have two working modules with the auto installed 2.4.4


I will prepare another message to the community what I would suggest for this kind of issues later on. But since I am not a long time member of Xoops I have already probably said too much and I hope everyone understands that my critics are neither against Xoops or anyone but I simply would like to point out some weak spots in the site and system.


Thanks for your understanding.

Thanks but in fact I believe I had the correct wf channel module.

Just for safety any issue with wflinks 1.08 does it interfere ???

What to do with it. Should I also uninstall before I install wf-resource.

and last not least do not know if you have read another thread aabout wflinks.

Everything seems to work except submission from the user side.

- no Thank you for ...... message.

only message:

it may take 48 to 72 hours after clicking the submission
( as someone suggested turn off disclaimer message, it was never turned on )

Thanks for your input, just do not want to do things twice and thrice if it can be avoided.

have installed the module wfresources but getting on the admin side from wf channel, when trying to update wfchannel


Update Failed: Required module WF-Resource is missing. Please Install this module and perform the update again

and also when calling the wfchannel module from the user side


_MA_WFC_ERROR_NOTUPDATE


my only reasoning could be because I might have uninstall wflinks

as well and then re-install and then update.

by the way I did that for wfchannel.

Ok guys I made now another Auto install of 2.4.4 from justhost.com uploaded the mxdirectory file from evucan, I even renamed it .

And it worked.

I tried another self install on another server ( they do not have autoinstall but it is the exaxt same php environment )

So there are 3 possibilities.

either

1) the files of 2.4.4 have not properly been uploaded by my FTP program but I doubt it because as I said it once worked.

2) there is somehow a difference between the version on justhost.com and the one on sourceforge.net

3) there is some issue during the self installattion.


I have done it now three times and always loaded up new files.



I am trying now to tell our hosting company to unzip the files on the server ( please do not suggest Shell access I know but I am not a programmer, but want just use it , ok )

Another request would be that you could provide me with this version of. 2.4.4 on justhost.com Fantastico installer.


Or you really have a look inside my server,
but I strongly believe that all files which should be up are up and during installation everything went fine without any troubles, well after several installation it is in fact a piece of cake to do it.


as you see I try very hard on every side but this line 1729 or now in fact 1730 error on the admin/index.php that can't be
true.

thanks for all your attention

thanks for the quick response and who knows that might also fix the sumbmission issue on wflinks we discussed earlier, but that would be strange because everything else seems to work with
wflinks on my site.

thanks for your answer but where can I get the wf-resource module, is it within the package of wf-channel. I could not find it in the repository, checked all modules with letter w.

thanks for you response

working , yes but only on one domain this has been yesterday, my problem exists on the new domain.

Sorry my problem is not solved I just wanted to point out, that the whole thing is very strange, and if you go back to the thread beginning you will realize that one guy has not been able and was not helped with his 2.4 version. He had the same problem on line 1729 admin/index.php

So his and my problem is still existing and if it would be any rather unimportant module I would drop the case and wait but I believe this is an essential module for every site and the matter should be resolved and since I am working with the current Xoops core I believe I am having a point. As you see Mamba is also working on the mxdirectory module. It seems he has realized the importance of such a module to work without trouble on the current or future versions.

that would be one plus point for xoops

thanks Mamba, I had found this version later on and yes the blank page issue is fixed.

And luckily on this thread domain where 2.4.4 is installed the module even works on the admin side in contrary to my installation on 2.4.4 on another domain.

which I have mentioned in another post

the issue with line 1729 on admin/index.php

I will most definitely not touch, uninstall or do anything else on the working module on this thread domain.

you might know due to several posts and mxdirectory module references on the threads I do have several version now of the
mxdirectory module but I am pretty certain the only one which is working at least on the user side is the once you suggested

evucan.

As I also said on the other post the very first install it worked on that server, too but I renamed it. But on the second install on that server it did not work anymore despite I was using the same module which is still working on the other domain.

I had downloaded the version from the working domain and uploaded the same module to the new installation on the other domain, but the result is the line 1729 error when calling the module in the admin panel.

( I also used a new version - freshly unzipped of evucan and the same result )


Strange thing but a fact.

Guys,

thanks for your input and in fact I am in discussion with Mamba about MX Directory on the current core version.

Once this is solved I will move to 2.4.4 with adslight and other modules I installed on 2.0,.16.

Generally most modules I am having on this version can be replaced with newer versions (compatible with 2.4.4 )

So I will opt for the upgrade or better new installation.
(Another reason for me is the already included protector module, which is a pain to install on the older versions )

However in my opinion the developers should separate modules
in the repository.

f.ex.
a) Modules for older versions
b)Modules for current version
c) Modules installed on current version of xoops.org

I mentioned in an earlier post that newcomers need a safe house in the beginning and if they break things later on with incompatible modules then no one can blame xoops because it was clearly seen that these modules are only for older versions.


Remark: I also would like to suggest since I have spent quite some time to evaluate Wordpress and how things are done with regard to modules ( they call it plugins )

Well if someone tries to install an incompatible module the user
gets a message in the admin panel.

Like: this plugin has not been tested with your version of wordpress, if you would like to continue then it is your ......................................................................

Unfortunately I am not a programmer but I believe this feature would definitely enhance the reputation of xoops .

Currently and it has always been, the module via core issue
is still a mXXX. Sorry but I cannot tell it in a more diplomatic way.

I strongly believe that you all do your best but a few warnings for the user especially at the introduction of the repository would save you as team and us as users/contributors a lot of hassle and time. you would have to spend less time for supporting these module issues.

INSTEAD of the

Welcome to the Official XOOPS Module Repository! in RED

there should be a few other commments in RED.

As I mentioned earlier I read at leat 2000 posts. but the average guy who would like to use a CMS ( xoops ) does not have that time and wants "JUST USE IT"

like open the door of a car and turn the key.

We all know it is not that easy.

But it could come close.

if there is a core with most used modules in the installer package.

These days most hosting companies anyway use the Auto-Installer.

THE PAST IS THE PAST AND CURRENT MEMBERS START TO KNOW ABOUT THE PROBLEMS I MENTIONED AND TRY TO SOLVE IT VIA TRYING ON THEIR OWN OR SEEKING SUPPORT.
THE LESS PERSISTENT ONES ALREADY HAVE GIVEN UP AND USE MOST PROBABLY NOW ANOTHER SYSTEM.

THE FUTURE AND FUTURE LESS PERSISTENT USERS SHOULD NOT BE CONFRONTED WITH THESE ISSUES ANYMORE SO THEY WILL BE HAPPY TO "just use it "

an entry message on the home page if this core with certain modules are once released should be.

Dear New Friends of Xoops,

once you have successfully setup (installed) your Xoops CMS platform please start to get accustomed with the process of
configuring the cores system and modules contained within Xoops.

We strongly advice to refrain installing other modules before you have not made at least one module work the way you want it.

This will not only save us all a lot of time in explaining and supporting you but give us precious time to improve, simplify and optimize the product of your choice.


P.S. with regard to wording some food for thought.

WP uses plugin and widgets

X uses modules and blocks.

my op it should be plugins and blocks

(Let us not forget that we should have a system which is also for non - native speakers - like me, you might have realized that on my upper construction of the suggested entry message )

So widget, no thank you
modules ?????

I know technically all these terms are correct.

Again things cannot be done from today until tomorrow and a little change on a website is definitely always a big issue.
THAT WAS JUST A SUGGESTION.