Hello

I had hope to turn-around or delay
the extensions compatibilities issues
but this free-extension is mandatory
and it look like to be a long-term working-with.


I installed just the free
com_alphauserpoints_v1.7.1.zip


but after some investigation on a mirror development site
it seems that exactly after applying
the "JMS patching-joomla-files" procedure
the initialization "AUP sync-user" procedure
fails with a 404 file not found.


The issue is reported here
www.alphaplug.com/index.php/forum/41-gen...ync-fails.html#18143

Would you please send us the extension in the attachement of an email to allow us try reproducing it.
See "contact us" for the email address.

...extension sent

available:

- The mirror development site
where destructive tests & patches can be done

- All the previous backups to restore if needed

Current versions are almost all the latest:
J2.51 jms1.2.73

Hello edwin2win

Stop checking alphauserpoints

I have seen that I was doing a bad backup-restore procedure.
With jms I have to change/revise all,
step-by-step including symlinks (as written in the FAQ)
I have to deal also with restore in different directories.
I will be back with results or further questions.

Just a question.
I noticed that jms patching doesn't write the php closing bracket "?>"
on the bottom of "configuration.php".
This done even the first time before any backups
Is that right?

Concerning the end of the "configuration.php" file and the "?>" this might be resulting of a fantastico installation that does not put the end of PHP at the end of the "configuration.php" file.

As JMS use the existing "configuration.php" to build the new one, this may result with a file with or without the "?>"

You will see that in joomla, several files does not close the PHP and this is not a problem.
Sometimes, it is recommended to avoid closing the PHP code to ensure that you don't have spaces or other characters after the end of the PHP.

We have correctly received the file that you sent us by email.
As you seems have idenitifed the reason of your problem, we will wait your additional feedback to analyze that more in detail.

Here I am

I got some good result with the revising of backup-restore proc.

The twin mirror site works well after moving to new directory and new database,
and the symbolic links this time have rebuilt right,
though it is not over yet, I have still to work on this issue.

So returning to the point:
the mirror site seems good but
the AUP sync-users initial procedure still fails.

Nonetheless I decided to do the same on the main site
and it fails there too.
This helps: as in this case there is not
any backup restore procedure involved.

So as I remember, the problem happens
when I apply the automatic jms patching procedure.

(jms is updated to 1.2.75)