SimplePortal

[GlitchPC]

Yeah, unfortunately there are some conflicts with the SMF Project Tools mod. I had to uninstall that mod before I could uninstall the old version of SimplePortal and install the new one over at simpleportal.net.

By the way, if you remove the portal.css file in your custom theme's directory, your portal should look better. It's using an outdated CSS file which results in problems with spacing between blocks.

I just removed the file...personally, I don't notice a difference.

[[SiNaN]]

Maybe you need to do a hard refresh (Ctrl+F5) on your browser.

Also, the "style" attribute of the last <img> tag in your "Follow Us!" block seems to be left open.

[GlitchPC]

How does it look now?

[[SiNaN]]

It looks okay now, yeah.

[GlitchPC]

Thanks, [SiNaN]...

[Angelina Belle]

teos55,

These 500 errors are always for such mysterious reasons.  I have had them for setting file and directory permissions TOO HIGH.
Good luck solving this. It is not directly related to Simple Portal, and perhaps not even so SMF...

[teos55]

 Thanks AngelinaBelle,

I faced another problem during backup/restore : http://www.simplemachines.org/community/index.php?topic=472332.0

I also suspect that, this is neither SP2.3.4 issue nor SMF.  Sure mine :-)))

I'll try the solution K@ has provided and feedback.

[teos55]

Solution provided by K@ has solved my issue with packages installed.  Now, my system is like before ..

Will begin the uninstall process of SP 2.3.4 shortly :-)  Taking necessary precautions ...

[teos55]

Angelinabelle ,

   Restarted uninstall process of SP 2.3.4  failed as before in ./index.php and ./Sources/Querystring.php

My question is ;

the very first one of 1 of 6 steps in ./index.php fails and
2 of 4 steps in /Sources/QueryString.php

What is your recommendation, should I continue to uninstall process and remove the above mentioned php lines manualy afterwards ?

Your help will be appreciated.

[NanoSector]

Though I'm not AngelinaBelle (heh), I'd recommend removing the code afterwards. Never do it beforehand, because if you failed to do it successfully it will crash the forum. Heck it even will afterwards but not that much.

Anyway, what's important is that you should remove the lines afterwards

[Angelina Belle]

Normally, I would uninstall ALL MODS in reverse order that they were installed until I came to simple portal, then uninstall and delete 2.3.4, then reinstall the others in the same order they are listed. Then install 2.3.5. 
This saves me the inevitable manual errors.

Alternatively, you can do as you suggested.  You can use the little icons to show EXACTLY where the failure is, hunt it down, make careful notes on what you need to do by hand, then uninstall via package manager and do the remaining edits yourself.  Only 2?

[Angelina Belle]

Yoshi is correct, too.

[teos55]

   Hımm,  crossing fingures and going the Yoshi's way, because the other method of removing all the mods till to sp 2.3.4 means
removing maybe 20 mods, and I'm sure they will fail in some way / somehow :-)))

[Angelina Belle]

If the went in OK, with no manual edits, they will go out ok.  If you had to make manual edits, then you are correct.
Yoshi's way will be easier.

[David111567]

upgraded on two of my sites....

and now my members cannot get into their blogs...

we use Adk Blog mod.  When I installed the new SP...this mod crashed.  Cannot locate problem.  Members are annoyed.

Suggestions?

David

[NanoSector]

Sorry, I think you'll have to fight with the ADK team for that, as Simple Portal is working correctly.

[Angelina Belle]

Did the ADK blog mod get along OK with previous Simple Portal versions?

[teos55]

   Hımm,  crossing fingures and going the Yoshi's way, because the other method of removing all the mods till to sp 2.3.4 means
removing maybe 20 mods, and I'm sure they will fail in some way / somehow :-)))

  Unfortunately, Yoshi's way didnot solve the problem.
Continued uninstall process.
modified /index.php  and /sources/querystring.php  afterwards

internal server error 500  comes up ....

I faced this problem before with file permissions, checked all the files one by one, all with proper permissions ...

if it is really a permission problem, why should uninstall process of sp 2.3.4 cause this ?  Wierd ...

Now, I'm stuck.  I had installed and uninstalled so many mods while sp2.3.4 active but never faced a problem ...

Any guidance ?  Sure,  removal of lines and files by sp2.3.4 uninstall process is causing this, but i cannot debug ...

To follow Angelinabelle's way, I have to remove 38 mods, (since sp 2.3.4 is the first one after smf 2.0.2 base code), which is not an easy job to do ...

[Angelina Belle]

At this point, I would suggest checking file ownership, and checking with your host.
It would seem that something is different between having the package manager do things, and having you copy the file down to your desktop, edit it, and copy it back up via FTP.

It could be important to find out what is the difference. 
What permission did you set on the offending file right before it started throwing the 500 error? 644 should be sufficient permission.
http://simpleportal.net/index.php?action=docs;area=solving_install_problems

[teos55]

All dirs have 755  and files 644 permissions.

  Maybe I should attach ./index and /Sources/querystring.php for a soul guy to modify them according to parse instr of sp2.3.4
for me.
  Appreciate if someone should help me .. 


nb. the result of sp 2.3.4  process also attached