First, change to the default theme and test a new registration. I say this because in an earlier post you mentioned trying to add some registration code yourself or something to that affect.

Secondly, and most likely, re-upload all your language files and make sure that the constants and translations are correct. For a test, you can upload the english language files and try to register.

Now, there is a good chance that none of the above will work. Sorry, I just popped online for a quick moment and couldn't leave your post un-answered with good concience.

You will not loose information or registered users upon a successful upgrade, however it is strongly reccomended at this time that you do not upgrade at this time.

there are several new features that have been added to the code that has had adverse effects on other code within the system.

I strongly recommend that you wait until the release of 2.3 and possibly 2.4 at the latest for a proper upgrade to take place. Development is underway to ensure that all users of all versions from 2.0.x on upwards wil have a smoth upgrade transition.

The only recommendation that I can make for you at this time is to upgrade from 2.0.13.1 to 2.0.13.2

Please read the recommended release notes here.

Evennews Mailer is a module for the XOOPS 2.0.x series.

It will import you current user base and allow them to add the option to a newsletter in their profile.

An alternative option would be to use a separate script for more professional looking emails with more options. All you would have to do is provide a link.

It all depends on how you want to implement the feature.

Good Luck

/yemplate_c is just a way for the system to create a repository for your viewed pages. Each time someone views a page, they will see a cached version for performance reasons. If you delete one of these files, it will get created again by the system upon refresh of that particular page.

One thing to keep in mind, is that when you edit your templates (in Templates administration for instance), your changes may not be noticed until you either delete the files in templates_c or enable the auto update feature that is built into the XOOPS administration area. That feature is handy when editing your templates, but should be turned off when your happy with your changes so that your site loads faster and doesn't look for a new template version for every ppage request. this can put a little bit of a strain on the overall performace of your site.

In general, you don't have to worry about it.

Also, if you edit any of your themes, (not templates, there is a difference), then you will also have to clear your cache to see the changes. CSS edits are normally reflected right away however.

I hope this helps clear things up for you a little bit.

Oh, and iff all that fails, then let us know what version of XOOPS you are installing and also you may want to simply overwrite your files with a fresh copy incase something got corrupted on transfer either way, or during decompression.

You never know with these things half of the time.

You seem to have all the pre-requisites need for a proper instalation.

All I can suggest for the moment is to open your mainfile.php (or reinstall from start) and make sure that your dsb is set for localhost and that your username and password for the db is correct.

I have in the past fought with my db for hours for simple oversites on my part.

What else...

I don't know, create your DB and make sure it is connectable and has access permissions. Create a separate user, give that user all privledges, create a password, use that info for your installation.

Let us know how it goes. Nine times out of ten, it's a misconfigured table prefix or password error.

Thanks for showing an interest in XOOPS Ed_Elric.

If you have any difficulties, what so ever, please feel free to post your questions here. If it's host related, domain related or XOOPS related, there is more talent and knowledge on these forums then you will find anywhere else.

Some recommendations for a beginning webmaster, if I may, would be to use http://www.godaddy.com. Just grab a starter package and go with it. Just a domain name registration and webhost, you don't need the other frills to get a good site running and you can upgrade at any time once your level of comfort has increased. Over time, as the months turn into years, you will be experienced enough to go out and get a different host. There is no need to go all over the place, comparing features and prices you know nothing about when there is a great serice on your doorstep to make the move simple, however, the experience in that task alone is more then worth the drive! We don't live in the dark ages anymore and some people just want to pull out the credit card and get online without the hassle of reading and researching. I can understand that, and this is the age to do it in. So go, point, click, get online and be done with it. Worry about the details after. When your done there, head straight back here!

Keep it simple, save yourself the frustration. They have impecable support (so do we), more FAQ's and help then you can shake a stick at (so do we). They offer incredible deals (although there are better deals price wise) for someone in your position. (and so do we- we're free!)

So long as your patient and don't freak out over a small problem, you will find the community here incredibly polite and helpful!

Good luck and congratulations on your decision to build a powerfull website with XOOPS!

I was just scoping out those specials last week. The VPS is a new service that looks real attractive and is starting to become more mainstream.

Thanks for sharing Kayla!

@ Basil

I'm not seeing this error anywhere on your site, unless I'm missing something. It almost looks like a bad or malformed language constant. More debugging info would be needed.

@ crystalmj924

Can you post a link to your site so we can see this in action please?

@ Both

Run some debugging if you can and post the results here. Also needed, are what modules and/or blocks you have running on the affected pages. It could be a block specific or module specific problem, but right now it's hard to tell without the proper details. Could you both provide some links and details on the final changes you made before you noticed this problem.

If anyone else in the community has seen or dealt with this problem first hand, please feel free to post what ever info you have. If it's a bug in the core, we would like to get rid it as soon as possible.

What exactly is Xipb? Is it a module, or separate script? I know what IPB is, but I can't say that I've ever heard of the one you have mentioned.

I would like to check the documentation to see if I could help. Can you provide a lin or two? I couldn't find anything here on the main site.