1111
redheadedrod
Re: Protector detects site manipulation

On my site, this showed no change.. emptying those did nothing...

Going to look at the protected directories as I saw mention of things on the support site where they must store stuff there...

But you would think if I disabled the module it should work..



1112
redheadedrod
Re: Protector detects site manipulation

I did do the deactivation as you prescribed but it didn't seem to deactivate the module.

I went into the database for that site, found the "_module" table and found the "protector" line in there, changed the 1 to a 0 for the isactive setting and hit submit.

I exited phpmysql and reentered it, went back and verified the setting was set correctly.

Went to the site and tried to access it and the protector line was still there.

I hit refresh more then once, exited my browser, restarted the computer and tried it again. I did not clear cookies but it should not have made a difference.

Scratching my head on this one. But then again, beta modules are beta for a reason...

And I did NOT put the patches to the core since Mamba mentioned they are no longer necissary with 2.4.3.

Rodney



1113
redheadedrod
Re: Protector detects site manipulation

And to clairify, The NEW site I put up has had nothing change in it physically. While setting it up and testing the base services I was able to access it via the URL, mysite.host.com. or in other words as a sub domain of host.com. I can STILL access the site in this manner (Although it still shows the same Protector error).

I have ADDED a method of getting to the web site however by changing the name server for the original web server which hosted the original mysite.com. Now when you go to mysite.com you go to the newer one which is also accessable by the mysite.host.com domain name.

I believe Protector got confused by the changing of the name server and being accessed by the mysite.com URL instead of mysite.host.com URL and has since shut down the site by displaying the above error and not providing a means for accessing the system.

I am busy today so I am hoping by putting this out here someone else has a suggestion. I will be addressing this one way or another on Saturday (US eastern time). Pending activation on the support site to ask about this there.

Rodney




1114
redheadedrod
Re: Protector detects site manipulation

Yes this is the error it shows. And no other information is available.

Weird thing is I did the same thing with another site and it did NOT do this...

Fortunately the site it did not happen with was the site I needed the most. I will likely back track to 3.4 or the 3.41 that was listed on the site as available.

If I were to manually uninstall Protector what areas do I need to look at?

I will likely look in the module files and try identifying the install script and basically try undoing it but I hate to do that not really knowing what all is effected outside of it. Since the sites I have this error on are in their infancy I can easily start from scratch but I will likely try to remove protector manually first before attempting this.

Assuming all there really is are the files in the docroot, trusted lib location and the database entries. Once I delete the database entries it should be as simple as deleting the two module directories and then going back and reinserting the older protector module or simply reinstalling the beta module.

Am I missing anything?

Thanks.

Rodney



1115
redheadedrod
Re: Protector detects site manipulation

I did this and verified it is correct in the database and it still is apparently active?

I do not have access to my site still.. Shows the same message.

I CAN just delete the site and restart it but was hoping not to...




1116
redheadedrod
Re: Protector detects site manipulation

Thanks, will give this a shot when i get home unless someone else has a better option.



1117
redheadedrod
Protector detects site manipulation

I have this error coming up on my web site and not sure how to reset it...

I have a new web hosting company and setup new sites for a couple sites I am running and got them running the way I wanted before I pointed the nameservers to them..

The sites were reached by the following URL..

newsite.host.com

where newsite was the new version of the old site and host.com is the main web page on my host...

When I transfered the sites nameservers over now I can access the new site with the following URL..

newsite.com

However I get the above error now and can not log into Xoops.

This is a fresh install with XOOPS 2.4.3 and Protector 3.5(Beta).

I am assuming that all I need to do is reset some flag in protector and it will work but how does this work?

I know no one has hacked the site so I know it is just due to my switching the name servers.

Hoping someone can offer a solution.

Thanks!

Rodney



1118
redheadedrod
Re: New Dokuwiki for Xoops release

Thank you, that time I got it downloaded fine...


Rodney



1119
redheadedrod
Re: New Dokuwiki for Xoops release

The download for this stalls at 25%. Is there another location we can download this from?

And which is better to make a wiki with this or mediawiki?

Thanks!

Rodney



1120
redheadedrod
Re: Having issues with Protector and 2.4.3 on clean install with included modules only

Ahh so you do not have to make changes to the mainfile.php file?

The patches to the databasefactory.php file?

I installed the beta 3.5 version of protector and it seems to work better but knows if you don't make the patches to the above to files. I have not had any errors with this version so far.

Protector does notice if you don't make the patches and will complain.

Rodney




TopTop
« 1 ... 109 110 111 (112) 113 114 115 116 »



Login

Who's Online

210 user(s) are online (134 user(s) are browsing Support Forums)


Members: 0


Guests: 210


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: May 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits