[Release] ENGLISH PowerWeb 3.0 - Updated for 4.7.5 server files

[NoBrain]

May I recommend you add the Patch Notes / Changelog in SPOILER tags so it doesn't clutter the main post if the list get very long?

Looks like a great project as well, not a huge fan of the design but that's just me being very picky.

[fallenfate]

May I recommend you add the Patch Notes / Changelog in SPOILER tags so it doesn't clutter the main post if the list get very long?

Looks like a great project as well, not a huge fan of the design but that's just me being very picky.

Oh definitely, the design is ridiculously bad, haha. Thanks for the tip about hiding the patch notes in Spoiler tags, definitely going to do that! Thanks also for the supportive comment! Thought it would be a good project to give back to the community since there are no other English files, and nothing above 3.2 nulled I believe, :).

I have a free theme coming for everyone that organises everything a lot nicer into an actual server website style.

Spoilers can't hurt, I'm a ex-web designer by trade, so here's a screenie of the theme layout (its a lot brighter, its dull because of web compression of the image; click here for the full image):

[fallenfate]

can't add item onwebshop ?

Error connect to xml: http://www.aiondatabase.com/xml/en_U.../125040231.xml

Please read the main post that I edited. You can add items on webshop, but not all. This problem cannot be fixed because items added to webshop use aiondatabase.com to get item stats to display in website, and aiondatabase.com is out-of-date. There is currently no up-to-date aion database anywhere with XML that we can use for PowerWeb. If the item you want to add is not on aiondatabase.com, it cannot be added.

I suppose maybe one way around it might be to make a webshop item in the category you want, then look in the database webshop table and copy the row, then edit in the item ID you want. But the item would not display any stats.

[vileninja]

you have some issues in your files.

Error 500
Error 500

Non-static method Status::server() should not be called statically, assuming $this from incompatible context

Strict standards: Non-static method Status::server() should not be called statically, assuming $this from incompatible context in C:\wamp\www\themes\default\views\main.php on line 117
Call Stack
#	Time	Memory	Function	Location
1	0.0005	242992	{main}( )	..\index.php:0
2	0.0178	1679048	CApplication->run( )	..\index.php:13
3	0.0178	1679280	CWebApplication->processRequest( )	..\CApplication.php:162
4	0.0370	1951464	CWebApplication->runController( )	..\CWebApplication.php:135
5	0.0409	2335320	CController->run( )	..\CWebApplication.php:276
6	0.0417	2380872	CController->runActionWithFilters( )	..\CController.php:266
7	0.0417	2381016	CController->runAction( )	..\CController.php:287
8	0.0418	2381104	CInlineAction->runWithParams( )	..\CController.php:309
9	0.0418	2381936	DroplistController->actionIndex( )	..\CInlineAction.php:50
10	0.0453	2648112	CController->render( )	..\DroplistController.php:57
11	0.0647	3923360	CBaseController->renderFile( )	..\CController.php:785
12	0.0648	3923456	CBaseController->renderInternal( )	..\CBaseController.php:96
13	0.0651	3943912	require( 'C:\wamp\www\themes\default\views\content.php' )	..\CBaseController.php:127
14	0.0661	4053192	CBaseController->endContent( )	..\content.php:4
15	0.0661	4053368	CBaseController->endWidget( )	..\CBaseController.php:301
16	0.0661	4053328	COutputProcessor->run( )	..\CBaseController.php:207
17	0.0661	4038072	CContentDecorator->processOutput( )	..\COutputProcessor.php:45
18	0.0661	4038232	CContentDecorator->decorate( )	..\CContentDecorator.php:55
19	0.0665	4038720	CBaseController->renderFile( )	..\CContentDecorator.php:77
20	0.0665	4038816	CBaseController->renderInternal( )	..\CBaseController.php:96
21	0.0671	4122200	require( 'C:\wamp\www\themes\default\views\main.php' )	..\CBaseController.php:127
22	0.0955	5382808	CApplication->handleError( )	..\CBaseController.php:117
23	0.0974	5541856	CErrorHandler->handle( )	..\CApplication.php:797
24	0.0975	5500760	CErrorHandler->handleError( )	..\CErrorHandler.php:110
25	0.0979	5534952	CErrorHandler->render( )	..\CErrorHandler.php:263
26	0.0980	5535000	CWebApplication->runController( )	..\CErrorHandler.php:305
27	0.0987	5590848	CController->run( )	..\CWebApplication.php:276
28	0.0988	5591536	CController->runActionWithFilters( )	..\CController.php:266
29	0.0988	5591680	CController->runAction( )	..\CController.php:287
30	0.0988	5591680	CInlineAction->runWithParams( )	..\CController.php:309
31	0.0988	5592216	SiteController->actionError( )	..\CInlineAction.php:50
32	0.0989	5593152	CController->render( )	..\SiteController.php:44
33	0.1001	5595384	CBaseController->renderFile( )	..\CController.php:785
34	0.1001	5595480	CBaseController->renderInternal( )	..\CBaseController.php:96
35	0.1004	5614616	require( 'C:\wamp\www\themes\default\views\content.php' )	..\CBaseController.php:127
36	0.1005	5632488	CBaseController->endContent( )	..\content.php:4
37	0.1005	5632664	CBaseController->endWidget( )	..\CBaseController.php:301
38	0.1005	5632584	COutputProcessor->run( )	..\CBaseController.php:207
39	0.1005	5616312	CContentDecorator->processOutput( )	..\COutputProcessor.php:45
40	0.1005	5616312	CContentDecorator->decorate( )	..\CContentDecorator.php:55
41	0.1009	5616768	CBaseController->renderFile( )	..\CContentDecorator.php:77
42	0.1010	5616864	CBaseController->renderInternal( )	..\CBaseController.php:96
43	0.1015	5698920	require( 'C:\wamp\www\themes\default\views\main.php' )	..\CBaseController.php

[fallenfate]

Those errors relate to your PHP configuration, not the files. I use VertrigoServ and have no issues, and I see you're using WAMP. You'll have to research those errors relating to WAMP's PHP.ini settings, as I don't use WAMP and have no internet besides my phone (just moved house).

[vileninja]

What version of php do you use? I think it has to do with the version to be completely honest. As they have updated how php works. You are no longer allowed to call the static functions the way it is done. I can fix some of the errors myself except the error 500. That relates to how the config calls stuff. Basically as far as i can see this site is so outdated that newer versions of php will not support it.

So if you could give me the version of php that you use maybe i can downgrade to that so it will work properly.

[fallenfate]

What version of php do you use? I think it has to do with the version to be completely honest. As they have updated how php works. You are no longer allowed to call the static functions the way it is done. I can fix some of the errors myself except the error 500. That relates to how the config calls stuff. Basically as far as i can see this site is so outdated that newer versions of php will not support it.

So if you could give me the version of php that you use maybe i can downgrade to that so it will work properly.

Sounds like another technically-minded person, welcome! :)

I am using PHP 5.3.27, with PhpMyAdmin 4.0.9 to administrate it, pulling data from MySQL 5.5.34.

[karl7]

You can fix this error by turning error_reporting to 0 or off, as per testing the website its working fine, tho some are not yet translated. and there a few you need to fix like the broker table columns, for droplist you have to convert the xml to sql if im not mistaken.

[NoBrain]

You can fix this error by turning error_reporting to 0 or off, as per testing the website its working fine, tho some are not yet translated. and there a few you need to fix like the broker table columns, for droplist you have to convert the xml to sql if im not mistaken.

Just turning off error reporting will only hide the errors and not actually fix them, therefore some features may not work since the errors are still happening just not being outputted to the website to be displayed publicly. It would be best if the developer looked into the errors and fixed them instead of recommending to just hide them. Errors will also slow down your website, quite massively according to some benchmarks I've seen.

[vileninja]

TBH im not sure about that one. I dont have that issue on my site. The droplist would almost be of no use to you as it looks at aiondatabase.com for the list and they are not even close to being up to date. They only support up to 2.7

- - - Updated - - -

Just turning off error reporting will only hide the errors and not actually fix them, therefore some features may not work since the errors are still happening just not being outputted to the website to be displayed publicly. It would be best if the developer looked into the errors and fixed them instead of recommending to just hide them. Errors will also slow down your website, quite massively according to some benchmarks I've seen.

You are 100% correct there. Although I see no slowing down on my site. I am going to eventually try and fix those errors by hand the correct way when i find the time.

[Maodao]

hello
How to enter the admin area?

thank you
Sorry for my bad English

[fallenfate]

You should make help topics in the Help section. But in short, just log-in through an admin game account and the admin area link appears.

[Maodao]

Perfect

Thank you

[Mennis343]

Really nice work on the site. One of the best ones I have came across or even laid eyes on :)

[fallenfate]

Really nice work on the site. One of the best ones I have came across or even laid eyes on :)

Thanks! I used to work in web design so I hoped it turned out alright, haha.