Hi Cavan,

Sorry I keep getting side tracked with this one , I have now set this site to notify me of any new posts in this thread.

Good to hear you've made some progress.

The "article saving failed" error comes about from a failed SQL statement which are located at lines 417 and 435 of class.newsstory.php. This means that the error *should* display itself if you turn on MySQL debug in your XOOPS preferences area. If you can turn on MySQL debug and then post the results from the MySQL debug window after you try submitting an article we should hopefully get some more insight.

I did a diff on your submit.php and it is exactly the same as the submit.php included with AMS 2.2. As I eluded to above, I think we will find that this is not a direct problem with AMS, but rather something to do with your environment that Xoops/AMS is not compatible with. Logic would suggest that if it was a problem (as in a bug) with AMS then there would be a lot of people reporting the same issue, which is not the case from what I have observed. Doesn't mean I don't want to get to the bottom of it though .

The [extend] tag is the tag AMS uses to seperate the article introduction from the main body of an article. All text prior to the [extend] tag is treated as the article introduction, and all text after it is treated as the main body of the article. For example;
Quote:
The fact that it is showing up when doing a preview is perfectly fine for AMS 2.2.

It might also be benefitial if you could turn on your PHP debuging options from within PHP itself. To do this set these values;

error_reporting = E_ALL

log_errors = On

error_log = path/to/file

This should hopefully also gives us some more information. I also wouldn't mind seeing what you exact PHP environment is. Could you place the following in a file with a .php extension;

Quote:

Doesn't matter what you call it, as long as it has a .php extension. Once you've done this could you PM me the URL so I can take a look.

Quote:

This occurs without having MySQL debug turned ON in the preferences menu.

Quote:

This issue began after the environment changes you suggested were made.


Quote:

I'm not sure how to do this since my site isn't hosted locally. Please let me know what to do here.

I've already posted my phpinfo.php, but that was prior to some of the environment changes. I'll PM a current phpinfo to you. The previous phpinfo results can be seen here. Thank you.

Quote:

Sorry, I shouldh've been clearer. The "article not saved" error is obviously not that helpful in terms of fault finding. What I am hoping is that we will be able to get an idea of exactly what is failing, and where by using the XOOPS MySQL debug option.

Quote:

Not sure what might have caused this not to show up prior, but obviously it was a PHP environment issue.

Quote:

I'm not an Apache man (I use IIS), but as far as I understand you should be able to set these options with your htaccess files.

Quote:

I've had a look at your PHP environment, and I'm struggling to see what might be causing it. The remaining issue might well lie outside your PHP config. I also just found out that if any sort of HTTP refferer blocking will also cause this type of behaviur, so it might be worth checking with your host to see if that is happening as well.

I turned on MySQL Debug but don't see any errors among the queries on any page. However, there is this error (when using PHP Debug) after clicking on the "preview" button when attempting to post a news item:

Warning [PHP]: array_push(): First argument should be an array in file class/module.textsanitizer.php line 113

The item will still post, even with this error being generated. I'm not sure what this means since I'm totally unfamiliar with the use of "textsanitizer" in XOOPS (or anywhere else for that matter). I don't understand why this error is generated when previewing a post (a post that isn't even using smilies). Below are lines 99-122 in my class/module.textsanitizer.php:



FYI, "array_push($this->smileys, $smiles);" is line 113 in my module.textsanitizer.php file.

Is this what's causing the problem with the news module[s]?

Getting somewhere...?

Okay, I deactivated and uninstalled AMS 2.2 and installed Stories 0.92, just to see if this module would work since I was having no luck with every other news module out there.
Guess what? It works, to an extent: I'm able to post with or without previewing the article, but yet another text sanitizer issue comes up with PHP Debug on:

...from modules/stories/index.php: (just visiting the page)

Warning [PHP]: Problem with method call - please report this bug in file modules/stories/class/class.newsstory.php line 138
Notice [PHP]: Undefined index: allowed_html in file modules/stories/class/stories_textsanitizer.php line 164
Notice [PHP]: Undefined index: allowed_html in file modules/stories/class/stories_textsanitizer.php line 164
Notice [PHP]: Undefined index: allowed_html in file modules/stories/class/stories_textsanitizer.php line 164
Notice [PHP]: Undefined index: allowed_html in file modules/stories/class/stories_textsanitizer.php line 164

...from modules/stores/submit.php: (no posting, just visiting the page)

Notice [PHP]: Undefined index: anonpost in file modules/stories/include/storyform.inc.php line 41

...from modules/stores/submit.php: (previewing the post but not submitting yet)

Notice [PHP]: Undefined index: allowed_html in file modules/stories/class/stories_textsanitizer.php line 188
Notice [PHP]: Undefined index: anonpost in file modules/stories/include/storyform.inc.php line 41

So, is there a definite issue with the module.textsanitizer.php on my site, or is it an environment problem? The problem exists with Stories 0.92 and AMS 2.2, so what's going on here? I'm stumped on this since I know nothing on the use of the "text sanitizer" (though I have a vague idea, that's all it is...a vague idea), or what it's purpose is in Xoops. Anyone?

Hi Cavan,

If you like, you can set up a test site on my server. Just to try and iron things out so you can see how things are meant to work. Perhaps that will give us an angle on why this problem is happening.

brash,

Let me know what you need me to do...Thanks.

in the middle of changing ISP Cavan, so I once I have that off my plate I can give this some more attention. What I will need is basically a copy of your database and XOOPS website so I can put them on my server and setup the site. You'd need to make a new DNS record to point to my server (something like beta.yourdomain.com ) . Before we do anything though can you check that your DNS hosting provider supports dynamic DNS?

Waiting on a RSVP from my host...I've downloaded a full backup of my site and have it available in a Zip. Let me know if this is acceptable. Thank you.

Hi Cavan,

That should be fine. Feel free to PM me with download details for your XOOPS and database backups .