استاذ ادهم مشكلة صغيرة بس وهي ان في تعليمات وتغييرات مع هاك تصغير الصور في ملفات المنتدي
Open the file includes/class_bbcode.php
Search the line(~line 1932 ):
ودي مهمة بالتاكيد
استاذ ادهم مشكلة صغيرة بس وهي ان في تعليمات وتغييرات مع هاك تصغير الصور في ملفات المنتدي
Open the file includes/class_bbcode.php
Search the line(~line 1932 ):
ودي مهمة بالتاكيد
بارك الله فيك
ممكن هذا الهاك
Living Avatars - vBulletin.org Forum
__________________
لـا خـيـر فـي كـاتـم الـعـلـمــــ
ياليت أخوي لو توفر لي هذا
DJ's AME (Auto Media Embedding) XML Media Definitions for AME 2.5 (Delta) - vBulletin.org Forum
vBTemplates - Custom templates anywhere - vBulletin.org Forum
v3 Arcade - Games Arcade System for 3.8.x - vBulletin.org Forum
vB Ad Management - vBulletin.org Forum
vMail - Verify Mail before registration. - vBulletin.org Forum
Imageshack & MEGAUPLOAD Uploader - vBulletin.org Forum
جزاك الله خير
__________________
No support via PM! to get support
Support Manger
تابع :1power:
__________________
No support via PM! to get support
Support Manger
تفضل
تم نقل الهاك على جزئين علشان المساحة
__________________
No support via PM! to get support
Support Manger
شكرا لك
لكن أناأبي الاستايل الرئيسي في موقعهم المستخدم الان
علما أني أملك عضوية في المنتدى
ولكن سألت وشوف وش قالوا
i need your blue style - vBulletin.org Forum
__________________
لا إله إلا الله محمدا رسول الله
هو ابلغك ان مكان وضع الموضوع خطا ... ويقولك ان الاستيل هذا خاص بالموقع ولاكن يمكن ان تسوي شيئ مثله بأى شركة تصميمات .
اخوى .. انتظر قليلا سوف اقوم بطرح الاستيل بخدمات ممتازة
__________________
No support via PM! to get support
Support Manger
الله يرحم والديك ويجعلك مع من احببت في الجنه
الجميع ان شاء الله وفى انتظار طرح الاستيل من الاخ دكتور كودر
واسف جداً لعدم دخولى هاليومين بسبب مشاكل الانترنت
__________________
مؤسسة كنترول
اسم الهاك :- 1.vBulletin-Blog-v2.0.
وظيفة الهاك :- مدونات الفى بى مثل الى بسوالف ( معرب )
اصدار الهاك :- 3.8.0
شرح التركيب :- - مرفق مع الهاك
تحميل الهاك :- أضغط هنا
__________________
مؤسسة كنترول
أخي ادهم اسف على الازعاج مقدما
احتاج الى هذه الصفحات و الهاكات
بالنسبة للهاكات فقط احتاج الهاك أما الصفحات فأحتاج المعلومات الموجودة في الصفحة دون الحاجة الى الصور
بعض الصفحات لا تحتوي هاكات و هي مجرد معلومات فلو كنت تقدر تنسخ لي المعلومات المخفية في ملف نصي أكون شاكر و مقدر لك
الهاكات
Facebook Connect - Allow your users to login with their Facebook account (for 3.8) - vBulletin.org Forum
LDAP Authentication - vBulletin.org Forum
OpenID Authentication - vBulletin.org Forum
Complete Wordpress/Vbulletin Bridge - Share Users And Postings - vBulletin.org Forum
الصفحات
Implementing CSRF Protection in modifications - vBulletin.org Forum
[How-To] vBulletin API Basics: Variables, Functions, Objects - vBulletin.org Forum
Custom Hooks - vBulletin.org Forum
[How-To] Extend and use the Session Table Effectively - vBulletin.org Forum
اعرف ان طلبي كبير لكني اعتقد أني احتاج لجميع الصفحات لعمل الفكرة التي اسعى لها
بارك الله فيك
__________________
http://servarica.com
Xen VPS and WHMCS Xen Management Addon modules
support@servarica.com
هلا بيك اخوى
نورت الموضوع ياغالى
اطلب اى شىء وانا تحت امرك
تفضل اولا الهاكات
والصفحات سيتم كمل كل موضوع برد منفرد
بالتوفيق
التعديل الأخير تم بواسطة ادهم وجدي ; 19-03-2009 الساعة 03:09 PM
__________________
مؤسسة كنترول
With the new version released today for vBulletin 3.6.10 and 3.7.0 RC4, a new protection against Cross Site Request Forgery (CSRF) has been introduced. This new protection might influence the coding in modifications.
Scott MacVicar took the time to compile a short explanation on this new protection for the coders on vBulletin.org:
Changes for CSRF protection with third party modifications
Cross Site Request Forgery (CSRF) involves taking advantage of the stateless nature of HTTP, there are no ways to ensure the exact origin of a request, its also not possible to detect what was actually initiated by a user and what was forced by a third party script. A token was added to the latest version of each of the vBulletin products, with the release of 3.6.10 and 3.7.0 RC4 it is no longer possible to submit a POST request directly without passing in the known token.
The addition of a security token for each POST request removes the ability for a remote page to force a user to submit an action. At the moment this protection will only apply to vBulletin files and third party files will need to opt into this protection and add the appropriate hidden field. This was done to preserve backwards compatibility.
Adding Protection to your own files
To opt your entire file into CSRF protection the following should be added to the top of the file under the define for THIS_SCRIPT.
With this change all POST requests to this file will check for the presence of the securitytoken field and compare it to the value for the user, if its wrong an error message will be shown and execution with halt.كود PHP:
define('CSRF_PROTECTION', true);
If this value is set to false then all CSRF protection is removed for the file, this is appropriate for something that intentionally accepts remote POST requests.
You should always add this to your file, even if you don't think the script is ever going to receive POST requests.
An absence of this defined constant within your files will result in the old style referrer checking being performed.
Template Changes
The following should be added to all of the forms which POST back to vBulletin or a vBulletin script. This will automatically be filled out with a 40 character hash that is unique to the user.
Again it is worthwhile adding this to your templates even if it is currently not using the CSRF protection.كود PHP:
<input type="hidden" name="securitytoken" value="$bbuserinfo[securitytoken]" />
Exempting Certain Actions
It may be appropriate to exempt a particular action from the CSRF protection, in this case you can add the following to the file.
The above example would exempt both example.php?do=action_one and example.php?do=action_two from the CSRF protection, if the CSRF_SKIP_LIST constant is defined with no value then it will exempt the default action.كود PHP:
define('CSRF_SKIP_LIST', 'action_one,action_two');
If the skip list needs to be changed at runtime is it available within the registry object, using the init_startup hook the following code would be used to exempt 'example.php?do=action_three'.
كود PHP:
if (THIS_SCRIPT == 'example')
{
$vbulletin->csrf_skip_list[] = 'action_three';
}
__________________
مؤسسة كنترول
vBulletin API Basics: Variables, Functions, Objects
THIS SHOULD NOT BE REPRINTED WITHOUT MY EXPLICIT PERMISSION
This How-To should serve as a reference to coders, who have a basic knowledge of PHP and who want to make their own mods.
$vbulletin (Type: Object)
Contains vBulletin data that has been in separate variables in vB 3.0.x.
Below you can find a translation table of changed variables and functions.
This is an expanded version of the list that you can find in vBulletin's source code (functions_legacy.php).
vBulletin 3.0.3 locations are on the left hand side, and the corresponding vBulletin 3.5.0 locations are on the right hand side.
Legacy locations can be enabled by running legacy_enable(), although this is officially not recommended for long term compatibility.
Please note the following:كود:* $vboptions['x'] --> $vbulletin->options['x'] * $iforumcache --> $vbulletin->iforumcache * $forumcache --> $vbulletin->forumcache * $usergroupcache --> $vbulletin->usergroupcache * $datastore['wol_spiders'] --> $vbulletin->wol_spiders * $smiliecache --> $vbulletin->smiliecache * $stylechoosercache --> $vbulletin->stylecache * $datastore['x'] --> $vbulletin->x * $bbuserinfo['x'] --> $vbulletin->userinfo['x'] * $session['x'] --> $vbulletin->session->vars['x'] * * $_BITFIELD['usergroup'] --> $vbulletin->bf_ugp * $_BITFIELD['usergroup']['x'] --> $vbulletin->bf_ugp_x * $_BITFIELD['usergroup']['x']['y'] --> $vbulletin->bf_ugp_x['y'] * $_BITFIELD['calmoderatorpermissions']['x'] --> $vbulletin->bf_misc_calmoderatorpermissions['x'] * $_BITFIELD['moderatorpermissions']['x'] --> $vbulletin->bf_misc_moderatorpermissions['x'] * $_BITFIELD['languageoptions']['x'] --> $vbulletin->bf_misc_languageoptions['x'] * $_USEROPTIONS['x'] --> $vbulletin->bf_misc_useroptions['x'] * $_FORUMOPTIONS['x'] --> $vbulletin->bf_misc_forumoptions['x'] * $_INTPERMS --> $vbulletin->bf_misc_intperms * $_INTPERMS['x'] --> $vbulletin->bf_misc_intperms['x'] * * ------------------------------------------------------------------------------ * Variables and Functions below are NOT affected/re-enabled by legacy_enable() * ------------------------------------------------------------------------------ * * $_GET/$_POST/$_REQUEST/$_COOKIE/$_FILES --> $vbulletin->GPC['x'] * $DB_Site->x() --> $vbulletin->db->x() * $url --> $vbulletin->url * $nozip --> $vbulletin->nozip * $script --> $vbulletin->script * $scriptpath --> $vbulletin->scriptpath * * HTML_SELECTED --> not defined anymore in vB 3.5 * HTML_CHECKED --> not defined anymore in vB 3.5 * * bbcode_parse() --> $bbcode_parser->parse * iif($condition, $r_true, $r_false) --> obsolete, use ($condition ? $r_true : $r_false) instead;
- $vbulletin
Inside of object classes, you should access $vbulletin->[...] as $this->registry->[...]. Therefore, use that structure when modifying code inside of any classes.
.- VARIABLES ENABLED FOR TEMPLATES
$vboptions['x'], $bbuserinfo['x'] and $session['x'] do work in the template system without running legacy_enable().
.- SUPERGLOBALS
$_GET/$_POST/$_REQUEST/$_COOKIE/$_FILES/$_SERVER/$_ENV are available anywhere, but generally you should avoid using them. Instead, "clean" those variables and place them into $vbulletin->GPC using $vbulletin->input->clean_gpc() and $vbulletin->input->clean_array_gpc() methods.
You can read more about these two "cleaning" methods here.
As a summary:
- Use $vbulletin->input->clean_gpc() for a single variable, and $vbulletin->input->clean_array_gpc() for arrays.
- After variables are patched through, they can be accessed using $vbulltin->GPC (which is an array).
- Cleaning 'somevar' will not create variable $somevar.
- $vbulletin->input->clean_gpc() returns the clean value, therefore the following code will work out nicely:
كود:$id = $vbulletin->input->clean_gpc('r', 'id', TYPE_UINT);
Once you get to know the syntax of those functions, you can use the following as a reference:
GLOBALIZING VARIABLES IN FUNCTIONSكود:------------------------------------ SOURCES AND THEIR EQUIVALENTS ------------------------------------ 'g' - $_GET 'p' - $_POST 'r' - $_REQUEST 'c' - $_COOKIE 's' - $_SERVER 'e' - $_ENV 'f' - $_FILES ------------------------------------ VALID DATA TYPES ------------------------------------ TYPE_BOOL - Boolean TYPE_INT - Integer TYPE_UINT - Unsigned Integer TYPE_NUM - Floating Point Number TYPE_UNUM - Unsigned Floating Point Number TYPE_UNIXTIME - Unix Timestamp (Unsigned Integer) TYPE_STR - Trimmed String (No leading or trailing whitespace) TYPE_NOTRIM - String TYPE_NOHTML - Trimmed String sent through htmlspecialchars_uni() TYPE_ARRAY - Array TYPE_FILE - File TYPE_NOCLEAN - Unvalidated
Since most of the variables can be found within the $vbulletin class, there is generally no need to globalize more than one variable (which is $vbulletin). An exception would be the $vbphrase array, which currently cannot be found within the $vbulletin class.
Taking the above account, the following code is not good:
كود:function foo() { global $forumcache, $vbulletin, $vboptions; $forumcache =& $vbulletin->forumcache; $vboptions =& $vbulletin->options; foreach ($forumcache AS $forumid => $forum) { if ($vboptions['something']) { // do stuff } } }
Instead, you should use the following code (which is, obviously, shorter and easier to use):
كود:function foo() { global $vbulletin; foreach ($vbulletin->forumcache AS $forumid => $forum) { if ($vbulletin->options['something']) { // do something } } }
DATASTORE ITEMS
In vBulletin 3.0.x you could commonly see the following code:
Unfortunately, this does not work in vBulletin 3.5.0, since the datastore items are now contained within $vbulletin class.كود PHP:
if (isset($datastore_item))
You need to use the following code instead:
كود PHP:
if ($vbulletin->datastore_item !== null)
if ($vbulletin->datastore_item !== null)
- BITFIELDS
In case you have been wondering, "ugp" stands for "UserGroup Permissions".
To avoid the confusing "$object->array[key1][key2][key3][key4]...[key10]" stuff, there are references set up that allow you to talk to deep elements quickly. For example, $vbulletin->bf_ugp_adminpermissions is a reference to $vbulletin->bf_ugp['adminpermissions'].
.- BBCODE PARSE
BBCode Parser has changed slightly in vBulletin 3.5.
To familiarize yourself with the new syntax, check out KirbyDE's How-To.
.- MISCELLANEOUS
It is impossible to list here every aspect of vBulletin code, therefore you should familizarize yourself with the contents of init.php and class_core.php before beginning to hack into the system (and I know you are in a rush ).
$db (Type: Object)
As you might have judged from the Table 1 in this tutorial, the database object in vB3.5 is $vbulletin->db.
However, $db is another way to access that object; it is the way that used everywhere unless you call it from within a function. In functions, use $vbulletin->db.
Obviously, the purpose of the database method is to perform various operations on the database. Most common methods are described below.
- $db->query();
Deprecated in favor of below methods (to save memory).
Returns: MySQL Resource
.- $db->query_read();
Performs SELECT and SHOW operations only.
These queries will execute on the slave server, if one is defined.
Returns: MySQL Resource
.- $db->query_write();
Performs INSERT, REPLACE, UPDATE, DROP, ALTER and other data-modifying queries.
These queries will execute on the master server.
Returns: MySQL Resource
.- $db->query_first();
Same as query_read(), but returns first result as an array.
Returns: array on success / boolean false on failure
.- $db->num_rows($mysql_resource_var);
Input: A MySQL resource variable (usually output of the first three methods).
Returns: int Amount of Resulting Rows
.- $db->fetch_array($mysql_resource_var);
Input: A MySQL resource variable (usually output of the first three methods).
Returns: array One row from the mysql results on success / boolean false on failure
To fetch each row consecutively, use the following code:يتابع هذا الردكود:while ($var = $db->fetch_array($mysql_resource_var)) { // your code ($var contains the array); }
__________________
مؤسسة كنترول